On Fri, Mar 13, 2015 at 03:27:01PM +0100, Thomas Graf wrote: > On 03/04/15 at 05:33pm, Ben Pfaff wrote: > > + If you want kernel datapath support for your new field, you also > > + need to modify the kernel module under the datapath/ (the Linux > > + datapath) or datapath-windows/ directory. This isn't mandatory, > > + since fields understood only by userspace work too (with a > > + performance penalty), so it's reasonable to start development > > + without it. > > Maybe add a reference to the upstream Linux kernel development process > as well. > > Acked-by: Thomas Graf <tg...@noironetworks.com>
Good point. I changed the paragraph to: If you want kernel datapath support for your new field, you also need to modify the kernel module for the operating systems you are interested in. This isn't mandatory, since fields understood only by userspace work too (with a performance penalty), so it's reasonable to start development without it. If you implement kernel module support for Linux, then the Linux kernel "netdev" mailing list is the place to submit that support first; please read up on the Linux kernel development process separately. The Windows datapath kernel module support, on the other hand, is maintained within the OVS tree, so patches for that can go directly to ovs-dev. and applied this to master. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
