Re: [ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

2019-03-20 Thread Ben Pfaff
On Thu, Mar 21, 2019 at 01:53:39AM +0530, Numan Siddique wrote: > On Wed, Mar 20, 2019, 11:43 PM Ben Pfaff wrote: > > > On Wed, Mar 20, 2019 at 05:06:36PM +0530, Numan Siddique wrote: > > > On Tue, Feb 12, 2019 at 8:41 AM Ben Pfaff wrote: > > > > I don't understand why icmp4.frag_mtu is so

Re: [ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

2019-03-20 Thread Numan Siddique
On Wed, Mar 20, 2019, 11:43 PM Ben Pfaff wrote: > On Wed, Mar 20, 2019 at 05:06:36PM +0530, Numan Siddique wrote: > > On Tue, Feb 12, 2019 at 8:41 AM Ben Pfaff wrote: > > > I don't understand why icmp4.frag_mtu is so heavily special-cased that > > > it only works inside nested actions. > > > >

Re: [ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

2019-03-20 Thread Ben Pfaff
On Wed, Mar 20, 2019 at 05:06:36PM +0530, Numan Siddique wrote: > On Tue, Feb 12, 2019 at 8:41 AM Ben Pfaff wrote: > > I don't understand why icmp4.frag_mtu is so heavily special-cased that > > it only works inside nested actions. > > The idea of this patch is to add new OVN fields which can't

Re: [ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

2019-03-20 Thread Numan Siddique
On Tue, Feb 12, 2019 at 8:41 AM Ben Pfaff wrote: > On Thu, Jan 10, 2019 at 11:30:58PM +0530, nusid...@redhat.com wrote: > > From: Numan Siddique > > > > In order to support OVN specific fields (which are not yet > > supported in OpenvSwitch to set or modify values) a generic > > OVN field

Re: [ovs-dev] [RFC v3 3/5] ovn: Add a new OVN field icmp4.frag_mtu

2019-02-11 Thread Ben Pfaff
On Thu, Jan 10, 2019 at 11:30:58PM +0530, nusid...@redhat.com wrote: > From: Numan Siddique > > In order to support OVN specific fields (which are not yet > supported in OpenvSwitch to set or modify values) a generic > OVN field support is added in this patch. These OVN fields are > expected to