OK.
On Tue, Dec 17, 2013 at 01:26:43PM -0800, Jesse Gross wrote: > At this point things are being added too frequently for it to be of > much use (for example, currently the most recent kernel that adds new > OVS features is the unreleased 3.13 RC). To me, it seems better to > include it in the documentation/log messages for individual features. > > On Tue, Dec 17, 2013 at 12:59 PM, Ben Pfaff <b...@nicira.com> wrote: > > I see your point, but I'm still sure users will want to know. Do we > > add new features in every kernel version? That is, can we say > > something like "3.x is the latest kernel version that adds new OVS > > features" or does that not make any sense? > > > > On Tue, Dec 17, 2013 at 12:53:25PM -0800, Jesse Gross wrote: > >> I think we would need to have a pretty large matrix of features and > >> kernel versions as this is no longer just about closing a gap between > >> upstream and out-of-tree. For example, IPFIX support went into both > >> places at the same time but not all upstream modules support it. Same > >> thing for TCP flags and megaflows (even though it's not directly > >> user-visible). Tunneling is really just one of those features at this > >> point. I think this is going to be hard to maintain (and will become > >> impossible once backported versions start showing up). > >> > >> On Tue, Dec 17, 2013 at 11:33 AM, Ben Pfaff <b...@nicira.com> wrote: > >> > Could we mention the kernel version that added support? It's going to > >> > be the next question people ask. > >> > > >> > On Tue, Dec 17, 2013 at 11:27:35AM -0800, Jesse Gross wrote: > >> >> Thanks for the review, I applied this to master. > >> >> > >> >> On Tue, Dec 17, 2013 at 11:21 AM, Pritesh Kothari (pritkoth) > >> >> <pritk...@cisco.com> wrote: > >> >> > looks good to me. > >> >> > > >> >> > Acked-by: pritesh <pritesh.koth...@cisco.com> > >> >> > > >> >> > On Dec 17, 2013, at 10:51 AM, Jesse Gross <je...@nicira.com> wrote: > >> >> > > >> >> >> Reported-by: Ben Pfaff <b...@nicira.com> > >> >> >> Signed-off-by: Jesse Gross <je...@nicira.com> > >> >> >> --- > >> >> >> FAQ | 23 +++++++++-------------- > >> >> >> 1 file changed, 9 insertions(+), 14 deletions(-) > >> >> >> > >> >> >> diff --git a/FAQ b/FAQ > >> >> >> index 2508c8c..3df1c54 100644 > >> >> >> --- a/FAQ > >> >> >> +++ b/FAQ > >> >> >> @@ -173,22 +173,17 @@ Q: Should userspace or kernel be upgraded > >> >> >> first to minimize downtime? > >> >> >> Q: What features are not available in the Open vSwitch kernel > >> >> >> datapath > >> >> >> that ships as part of the upstream Linux kernel? > >> >> >> > >> >> >> -A: The kernel module in upstream Linux 3.3 and later does not > >> >> >> include > >> >> >> - tunnel virtual ports, that is, interfaces with type "gre", > >> >> >> - "ipsec_gre", "gre64", "ipsec_gre64", "vxlan", or "lisp". It is > >> >> >> - possible to create tunnels in Linux and attach them to Open > >> >> >> vSwitch > >> >> >> - as system devices. However, they cannot be dynamically created > >> >> >> - through the OVSDB protocol or set the tunnel ids as a flow > >> >> >> action. > >> >> >> - > >> >> >> - Work is in progress in adding tunnel virtual ports to the > >> >> >> upstream > >> >> >> - Linux version of the Open vSwitch kernel module. For now, if you > >> >> >> - need these features, use the kernel module from the Open vSwitch > >> >> >> +A: The kernel module in upstream Linux does not include support for > >> >> >> + LISP. Work is in progress to add support for LISP to the upstream > >> >> >> + Linux version of the Open vSwitch kernel module. For now, if you > >> >> >> + need this feature, use the kernel module from the Open vSwitch > >> >> >> distribution instead of the upstream Linux kernel module. > >> >> >> > >> >> >> - The upstream kernel module does not include patch ports, but this > >> >> >> - only matters for Open vSwitch 1.9 and earlier, because Open > >> >> >> vSwitch > >> >> >> - 1.10 and later implement patch ports without using this kernel > >> >> >> - feature. > >> >> >> + Certain features require kernel support to function or to have > >> >> >> + reasonable performance. If the ovs-vswitchd log file indicates > >> >> >> that > >> >> >> + a feature is not supported, consider upgrading to a newer > >> >> >> upstream > >> >> >> + Linux release or using the kernel module paired with the > >> >> >> userspace > >> >> >> + distribution. > >> >> >> > >> >> >> Q: What features are not available when using the userspace datapath? > >> >> >> > >> >> >> -- > >> >> >> 1.8.3.2 > >> >> >> > >> >> >> _______________________________________________ > >> >> >> dev mailing list > >> >> >> dev@openvswitch.org > >> >> >> http://openvswitch.org/mailman/listinfo/dev > >> >> > > >> >> _______________________________________________ > >> >> dev mailing list > >> >> dev@openvswitch.org > >> >> http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
