On Thu, Jun 11, 2015 at 06:01:42PM +, Gray, Mark D wrote:
> As a general comment, why didn’t you pluginize (if that is a word) the
> current set of netdevs and ofprotos in this patch?
That's the direction that I think we'd have to go for this kind of thing
to be maintainable. If the community
On Wed, Jun 10, 2015 at 01:15:21AM -0700, michael.zay...@hp.com wrote:
> 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 appropri
> -Original Message-
> From: Gray, Mark D [mailto:mark.d.g...@intel.com]
> Sent: Thursday, June 11, 2015 11:02 AM
> To: Zayats, Michael; dev@openvswitch.org
> Subject: RE: [ovs-dev] [PATCH] vswitchd: adding plugin infrastructre
>
> >
> > Per this patch ov
>
> 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 functio
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.
Currently, the main purpose is to allow in
