From: Thomas F Herbert <thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ccp-HUUA3fb44xqsTnJN9+BGXg@public.gmane.org,
dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org,
therbert-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Thomas F Herbert
<thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH net-next V8 0/2] openvswitch: Add support for 802.1AD
Date: Tue, 5 May 2015 11:51:25 -0400 [thread overview]
Message-ID: <1430841087-20764-1-git-send-email-thomasfherbert@gmail.com> (raw)
Add support for 802.1AD to the openvswitch kernel module (Version 8.)
Please replace version 7 submitted on April 25, with this patch.
Version 8 has changes based on the review by Pravin Shelar of V7 and a fix
to flow.c to initialize the ctci in the flow key.
There was one recommended change from the review that was not made in this
patch about a double check for vlan headers. The rationale for not making
that change will be explained separately.
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 patch addresses adds 802.1ad to the
Linux kernel openvswitch data path.
This patch is version 8 of the patch andccompanies user space version 7 of
the patch previously submitted separately 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 | 94 +++++++++++++++++++++++++++++++++++++---
5 files changed, 174 insertions(+), 27 deletions(-)
--
2.1.0
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
next reply other threads:[~2015-05-05 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:51 Thomas F Herbert [this message]
[not found] ` <1430841087-20764-1-git-send-email-thomasfherbert-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-05 15:51 ` [PATCH net-next V8 1/2] openvswitch: 802.1ad uapi changes Thomas F Herbert
2015-05-05 15:51 ` [PATCH net-next V8 2/2] openvswitch: 802.1ad: Flow handling, actions, and parsing Thomas F Herbert
2015-05-06 18:36 ` [ovs-dev] " Pravin Shelar
2015-05-13 0:04 ` 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=1430841087-20764-1-git-send-email-thomasfherbert@gmail.com \
--to=thomasfherbert-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ccp-HUUA3fb44xqsTnJN9+BGXg@public.gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=therbert-H+wXaHxf7aLQT0dZR+AlfA@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).