From: Thomas F Herbert <thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
Thomas F Herbert
<thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH net-next V7 0/2] openvswitch: Add support for 802.1AD
Date: Sun, 26 Apr 2015 14:33:00 -0400 [thread overview]
Message-ID: <1430073182-14195-1-git-send-email-thomasfherbert@gmail.com> (raw)
Add support for 802.1AD to the openvswitch kernel module.
Although the Open Flow specification specified support for 802.1AD (qinq)
as well as push and pop vlan headers, So far Open vSwitch has only
supported a single tag header.
This accompanies version 7 of the patch submitted to openvswitch dev list.
For discussion, history and previous versions, of the kernel patch,
see the OVS dev mailing list, openvswitch.org/pipermail/dev/..
Thomas F Herbert (2):
add flow key field for ctag
Flow handling, actions, and vlan parsing for 8021AD
include/uapi/linux/openvswitch.h | 17 ++++----
net/openvswitch/actions.c | 6 ++-
net/openvswitch/flow.c | 83 +++++++++++++++++++++++++++++++++-------
net/openvswitch/flow.h | 1 +
net/openvswitch/flow_netlink.c | 81 ++++++++++++++++++++++++++++++++++++---
5 files changed, 160 insertions(+), 28 deletions(-)
--
2.1.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
next reply other threads:[~2015-04-26 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 18:33 Thomas F Herbert [this message]
2015-04-26 18:33 ` [PATCH net-next V7 1/2] net: openvswitch: 802.1ad uapi changes Thomas F Herbert
2015-04-26 18:33 ` [PATCH net-next V7 2/2] net: openvswitch: 802.1ad: Flow handling, actions, and vlan parsing Thomas F Herbert
2015-04-27 3:03 ` [PATCH net-next V7 0/2] openvswitch: Add support for 802.1AD David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-04-28 22:44 Thomas F Herbert
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=1430073182-14195-1-git-send-email-thomasfherbert@gmail.com \
--to=thomasfherbert-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).