On Fri, Sep 07, 2018 at 09:43:09AM -0400, Eric Garver wrote:
> On Fri, Sep 07, 2018 at 09:58:16AM +, Lilijun (Jerry, Cloud Networking)
> wrote:
> > We can remove the unlimited words. Maybe like this:
> >
> > Value 0 means the max number of VLANs supported by Open
> > vSw
On Fri, Sep 07, 2018 at 09:58:16AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> We can remove the unlimited words. Maybe like this:
>
> Value 0 means the max number of VLANs supported by Open
> vSwitch userspace (currently 2), or the number
> supported by
We can remove the unlimited words. Maybe like this:
Value 0 means the max number of VLANs supported by Open
vSwitch userspace (currently 2), or the number
supported by the datapath.
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Friday,
Sorry, I will push it again to fix this error.
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Friday, September 07, 2018 12:20 PM
To: Lilijun (Jerry, Cloud Networking)
Cc: ovs-disc...@openvswitch.org; d...@openvswitch.org; Eric Garver
Subject: Re: [ovs-discuss] [PATCH]
On Fri, Sep 07, 2018 at 02:54:18AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> Hi all,
>
> In my test, vlan-limit is set to 0 that means unlimited the count of vlan
> headers.
> ovs-vsctl set Open_vSwitch . other_config:vlan-limit=0
>
> But in fact the macro FLOW_MAX_VLAN_HEADERS is define
On Fri, Sep 07, 2018 at 02:51:25AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> In my test, vlan-limit is set to 0 that means unlimited the count of vlan
> headers.
> ovs-vsctl set Open_vSwitch . other_config:vlan-limit=0
>
> But in fact the macro FLOW_MAX_VLAN_HEADERS is defined as 2, so we