> > Per this patch ovs-vswitchd searches for shared objects, with > a certain set of exposed routines, in a specific configurable path. > Once found, all compatible plugins are loaded and their routines are > called at appropriate points of the daemon execution. >
Personally, I like this functionality. I didn’t do a full review as I wanted to see what others thought of it. What is your use case for this? Do you want to distribute a netdev as a binary blob? Is there any reason you left out the dpif? Previously, we maintained a separate dpif-provider and I often wanted us to just provide the dpif code in our repo and plug it into the upper layers of ovs. However even if we did this, one of the problems that we would have faced was that the dpif interface changed quite regularly and was difficult to maintain (it was a nightmare when megaflows were introduced!). So in our case, I kind of felt to get the real value out of this we would need some kind of stability in the ABI/API of the dpif interface. As a general comment, why didn’t you pluginize (if that is a word) the current set of netdevs and ofprotos in this patch? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
