netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Garver <e@erig.me>
To: netdev@vger.kernel.org
Cc: dev@openvswitch.org, Thomas F Herbert <thomasfherbert@gmail.com>,
	Xiao Liang <shaw.leon@gmail.com>
Subject: [PATCH net-next v22 0/3] openvswitch: add 802.1ad support
Date: Wed,  7 Sep 2016 12:56:56 -0400	[thread overview]
Message-ID: <1473267419-6825-1-git-send-email-e@erig.me> (raw)

This series adds 802.1ad support to openvswitch. It is a continuation of the
work originally started by Thomas F Herbert - hence the large rev number.

The extra VLAN is implemented by using an additional level of the
OVS_KEY_ATTR_ENCAP netlink attribute.
In OVS flow speak, this looks like

   eth_type(0x88a8),vlan(vid=100),encap(eth_type(0x8100), vlan(vid=200),
                                        encap(eth_type(0x0800), ...))

The userspace counterpart has also seen recent activity on the ovs-dev mailing
lists. There are some new 802.1ad OVS tests being added - also on the ovs-dev
list. This patch series has been tested using the most recent version of
userspace (v3) and tests (v2).

v22 changes:
  - merge patch 4 into patch 3
  - fix checkpatch.pl errors
    - Still some 80 char warnings for long string literals
  - refresh pointer after pskb_may_pull()
  - refactor vlan nlattr parsing to remove some double checks
  - introduce ovs_nla_put_vlan()
  - move triple VLAN check to after ethertype serialization
  - WARN_ON_ONCE() on triple VLAN and unexpected encap values

v21 changes:
  - Fix (and simplify) netlink attribute parsing
  - re-add handling of truncated VLAN tags
  - fix if/else dangling assignment in {push,pop}_vlan()
  - simplify parse_vlan()


Eric Garver (2):
  vlan: Check for vlan ethernet types for 8021.q or 802.1ad
  openvswitch: 802.1AD Flow handling, actions, vlan parsing, netlink
    attributes

Thomas F Herbert (1):
  openvswitch: 802.1ad uapi changes.

 include/linux/if_vlan.h          |  33 +++--
 include/uapi/linux/openvswitch.h |  17 ++-
 net/openvswitch/actions.c        |  16 +-
 net/openvswitch/flow.c           |  65 +++++---
 net/openvswitch/flow.h           |   8 +-
 net/openvswitch/flow_netlink.c   | 310 ++++++++++++++++++++++++++-------------
 net/openvswitch/vport.c          |   7 +-
 7 files changed, 314 insertions(+), 142 deletions(-)

-- 
2.5.5

             reply	other threads:[~2016-09-07 16:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 16:56 Eric Garver [this message]
     [not found] ` <1473267419-6825-1-git-send-email-e-jCUjZXiOoP8@public.gmane.org>
2016-09-07 16:56   ` [PATCH net-next v22 1/3] openvswitch: 802.1ad uapi changes Eric Garver
     [not found]     ` <1473267419-6825-2-git-send-email-e-jCUjZXiOoP8@public.gmane.org>
2016-09-08  1:20       ` pravin shelar
2016-09-07 16:56 ` [PATCH net-next v22 2/3] vlan: Check for vlan ethernet types for 8021.q or 802.1ad Eric Garver
     [not found]   ` <1473267419-6825-3-git-send-email-e-jCUjZXiOoP8@public.gmane.org>
2016-09-08  1:20     ` pravin shelar
2016-09-07 16:56 ` [PATCH net-next v22 3/3] openvswitch: 802.1AD Flow handling, actions, vlan parsing, netlink attributes Eric Garver
     [not found]   ` <1473267419-6825-4-git-send-email-e-jCUjZXiOoP8@public.gmane.org>
2016-09-08  1:20     ` pravin shelar
2016-09-09  0:11 ` [PATCH net-next v22 0/3] openvswitch: add 802.1ad support David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1473267419-6825-1-git-send-email-e@erig.me \
    --to=e@erig.me \
    --cc=dev@openvswitch.org \
    --cc=netdev@vger.kernel.org \
    --cc=shaw.leon@gmail.com \
    --cc=thomasfherbert@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).