[ovs-dev] [PATCH 1/2] : 802.1ad support in OVS & OVS-DPDK

Jesse Gross jesse at kernel.org
Wed Feb 17 17:05:42 UTC 2016


In addition, there have been numerous revisions of a previous patch
series that implements this. I believe that this is the most recent
one:
http://openvswitch.org/pipermail/dev/2015-November/061861.html

Please work with that author instead of starting from scratch.

On Wed, Feb 17, 2016 at 6:49 AM, Aaron Conole <aconole at redhat.com> wrote:
> Apologies for the top post. This post and your subsequent 2/2 have a few
> flaws:
>
> 1. The signed-off-by line is mangled (assuming that is done by your mail
>    client)
> 2. it appears to be against 2.4 branch (why not against master, should
>    be good to explain this in the scissors section)?
> 3. The spacing in the code does not make sense.
> 4. The 'thanks' signature should be removed (makes generating a diff
>    very difficult).
> 5. My personal opinion is the blob of text at the end is inappropriate
>    for an open source mailing list, but no matter it prevents creating a
>    proper diff from this email.
>
> See CONTRIBUTING.md and CodingStyle.md for more
> information. Specifically the format of diffs and how to configure your
> mail client.
>
> Thanks for your attention,
> -Aaron
>
> <gayathri.manepalli at wipro.com> writes:
>
>> Hi All,
>> Below are the configuration and patch details which provides the 802.1ad support
>> for OVS.
>> Description & configuration :
>> OVS supports the following port types with respect to configuration and
>> datapath handling.
>> 1. Access
>> 2. Trunk
>> 3. Native-tagged.
>> 4. Native-untagged.
>> Access port adds vlan header on ingress and removes vlan header on egress
>> By default trunk passes every VLAN traffic if not configured with any specific
>> VLAN ID's
>> A native-tagged port resembles a trunk port, with the exception that a packet
>> without an 802.1Q header that ingresses on a native-tagged port is in the
>> ''native VLAN'' (specified in the tag column).
>>
>> A native-untagged port resembles a native-tagged port, with the exception that
>> a packet that egresses on a native-untagged port in the native VLAN will not
>> have an 802.1Q header (pop).
>>
>> Apart from above 4, to enable 802.1ad, we have introduced a new mode called
>> "trunk-qinq"
>> Trunk-qinq port operational modes:
>> Trunk-qinq port can be configured to work in two modes shown below
>>
>> 1.       Default mode.
>>
>> 2.       Qualified C-VLAN mode.
>> Default mode: When you just configure a port as trunk-qinq port as below, it
>> falls into default mode
>>        $ovs-vsctl set port eth0 tag=118 vlan_mode=trunk-qinq
>> In Default mode, a trunk-qinq port adds 802.1ad vlan header with vid = <118>
>> for every C-VLAN tagged traffic received on ingress.
>> On egress if the packet to be sent out is already 1ad tagged with vid =<118>
>> then removes the 1ad vlan header and send it out to the trunk port of
>> customer edge bridge.
>> Qualified C-VLAN mode:  A trunk-qinq port can be set to work in Qualified
>> C-VLAN mode as follows.
>>        $ovs-vsctl set port eth0 tag=118 vlan_mode=trunk-qinq cvlans=10, 20, 30
>> In Qualified C-VLAN mode, a trunk-qinq port adds 802.1ad vlan header with
>> vid = <118> only for qualified C-VLANS mentioned in cvlans=10, 20, 30.
>> Qualified cvlans are nothing but a set of specific cvlan's receiving from
>> customer; which are to be designated for 802.1ad tunneled.
>> On egress if the packet to be sent out is already 1ad tagged with vid =<118>
>> then removes the 1ad vlan header and send it out to the trunk port of
>> customer edge bridge.
>>
>> Signed-off-by: Manepalli S Gayathri gayathri.manepalli at wipro.com<mailto:gayathri.manepalli at wipro.com>



More information about the dev mailing list