Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Yang, Yi
On Tue, Aug 15, 2017 at 12:09:14AM +0800, Eric Garver wrote: > On Thu, Aug 10, 2017 at 09:21:15PM +0800, Yi Yang wrote: > > Hi Yi, > > In general I'd like to echo Jiri's comments on the netlink attributes. > I'd like to see the metadata separate. > > I have a few other comments below. > > Thank

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Eric Garver
On Thu, Aug 10, 2017 at 09:21:15PM +0800, Yi Yang wrote: > OVS master and 2.8 branch has merged NSH userspace > patch series, this patch is to enable NSH support > in kernel data path in order that OVS can support > NSH in 2.8 release in compat mode by porting this. > > Signed-off-by: Yi Yang > -

RE: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Jan Scheurich
> From: Jiri Benc [mailto:jb...@redhat.com] > Sent: Monday, 14 August, 2017 12:48 > > On Mon, 14 Aug 2017 10:35:42 +, Jan Scheurich wrote: > > Is it worth to speculate on how a hypothetical future NSH version > > (with a different Version value in the Base header) might look like? > > Absolut

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Jiri Benc
On Mon, 14 Aug 2017 10:35:42 +, Jan Scheurich wrote: > Is it worth to speculate on how a hypothetical future NSH version > (with a different Version value in the Base header) might look like? Absolutely. This is uAPI we're talking about and once merged, it's set in stone. Whatever we come up w

RE: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Jan Scheurich
> From: Jiri Benc [mailto:jb...@redhat.com] > Sent: Monday, 14 August, 2017 09:51 > > On Sun, 13 Aug 2017 21:13:57 +, Jan Scheurich wrote: > > Jiri, I am not too familiar with conventions on the OVS netlink > > interface regarding the handling of variable length fields. What is > > the benefit

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-14 Thread Jiri Benc
On Sun, 13 Aug 2017 21:13:57 +, Jan Scheurich wrote: > Jiri, I am not too familiar with conventions on the OVS netlink > interface regarding the handling of variable length fields. What is > the benefit of structuring the push_nsh action into > > OVS_ACTION_ATTR_PUSH_NSH > +-- OVS_ACTION_ATTR_

RE: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-13 Thread Jan Scheurich
> From: Jiri Benc [mailto:jb...@redhat.com] > Sent: Friday, 11 August, 2017 12:23 > > On Fri, 11 Aug 2017 10:09:36 +, Jan Scheurich wrote: > > Unless someone can explain to me why the datapath should understand the > > internal structure/format of metadata in push_nsh, I would strongly > > vot

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jiri Pirko
Fri, Aug 11, 2017 at 12:09:36PM CEST, jan.scheur...@ericsson.com wrote: >> -Original Message- >> From: Jiri Benc [mailto:jb...@redhat.com] >> Sent: Friday, 11 August, 2017 11:45 >> >> The context field does not apply to MD type 2. It looks wrong for the >> context field to be included in n

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jiri Benc
On Fri, 11 Aug 2017 10:09:36 +, Jan Scheurich wrote: > Unless someone can explain to me why the datapath should understand the > internal structure/format of metadata in push_nsh, I would strongly > vote to keep the metadata as variable length octet sequence in the > non-structured OVS_ACTION_A

RE: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jan Scheurich
> -Original Message- > From: Jiri Benc [mailto:jb...@redhat.com] > Sent: Friday, 11 August, 2017 11:45 > > The context field does not apply to MD type 2. It looks wrong for the > context field to be included in netlink attribute for anything other > than MD type 1. Perhaps it needs to be p

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Yang, Yi
On Fri, Aug 11, 2017 at 11:44:49AM +0200, Jiri Benc wrote: > On Fri, 11 Aug 2017 09:24:25 +, Yang, Yi Y wrote: > > So far, we're not clear how we can support MD type 2 better, as I > > explained before, we need to reuse tun_metadata in struct flow_tnl > > which is the thing Geneve is using. Gen

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jiri Benc
On Fri, 11 Aug 2017 09:24:25 +, Yang, Yi Y wrote: > So far, we're not clear how we can support MD type 2 better, as I > explained before, we need to reuse tun_metadata in struct flow_tnl > which is the thing Geneve is using. Geneve predefined 64 keys for > this from tun_metadata0 to tun_metadat

RE: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Yang, Yi Y
, Yi Y Cc: netdev@vger.kernel.org; d...@openvswitch.org Subject: Re: [PATCH net-next v2] openvswitch: enable NSH support On Fri, 11 Aug 2017 16:47:23 +0800, Yang, Yi wrote: > is "__be32 context[4]" ok? Yes, that looks better. > So define three new netlink attributes > >

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jiri Benc
On Fri, 11 Aug 2017 16:47:23 +0800, Yang, Yi wrote: > is "__be32 context[4]" ok? Yes, that looks better. > So define three new netlink attributes > > OVS_ACTION_ATTR_NSH_BASE_HEADER > OVS_ACTION_ATTR_NSH_MD1_DATA > OVS_ACTION_ATTR_NSH_MD2_DATA > > OVS_ACTION_ATTR_PUSH_NSH is nested netlink attr

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Yang, Yi
On Fri, Aug 11, 2017 at 10:24:18AM +0200, Jiri Benc wrote: > On Thu, 10 Aug 2017 21:21:15 +0800, Yi Yang wrote: > > OVS master and 2.8 branch has merged NSH userspace > > patch series, this patch is to enable NSH support > > in kernel data path in order that OVS can support > > NSH in 2.8 release i

Re: [PATCH net-next v2] openvswitch: enable NSH support

2017-08-11 Thread Jiri Benc
On Thu, 10 Aug 2017 21:21:15 +0800, Yi Yang wrote: > OVS master and 2.8 branch has merged NSH userspace > patch series, this patch is to enable NSH support > in kernel data path in order that OVS can support > NSH in 2.8 release in compat mode by porting this. Please include changelog when posting