From: William Tu <u9012063@gmail.com>
To: netdev@vger.kernel.org
Cc: pshelar@ovn.org, jbenc@redhat.com
Subject: [PATCHv3 net-next 0/2] net: erspan: add support for openvswitch
Date: Wed, 17 Jan 2018 09:32:49 -0800 [thread overview]
Message-ID: <1516210371-20732-1-git-send-email-u9012063@gmail.com> (raw)
The first patch refactors the erspan header definitions.
Originally, the erspan fields are defined as a group into a __be16 field,
and use mask and offset to access each field. This is more costly due to
calling ntohs/htons and error-prone. The first patch changes it to use
bitfields. The second patch introduces the new OVS tunnel key attribute
to program both v1 and v2 erspan tunnel for openvswitch.
William Tu (2):
net: erspan: use bitfield instead of mask and offset
openvswitch: add erspan version I and II support
include/net/erspan.h | 127 +++++++++++++++++++++++---------
include/uapi/linux/openvswitch.h | 11 +++
net/ipv4/ip_gre.c | 38 ++++------
net/ipv6/ip6_gre.c | 36 ++++-----
net/openvswitch/flow_netlink.c | 154 ++++++++++++++++++++++++++++++++++++++-
5 files changed, 285 insertions(+), 81 deletions(-)
---
v2->v3
revert the "openvswitch: Add erspan tunnel support." commit ceaa001a170e.
redesign the OVS_TUNNEL_KEY_ATTR_ERSPAN_OPTS as nested attribute
v1->v2
Fix compatibility issue suggested by Pravin.
-
2.7.4
next reply other threads:[~2018-01-17 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:32 William Tu [this message]
2018-01-17 17:32 ` [PATCHv3 net-next 1/2] net: erspan: use bitfield instead of mask and offset William Tu
2018-01-17 17:32 ` [PATCHv3 net-next 2/2] openvswitch: add erspan version I and II support William Tu
2018-01-18 10:13 ` Jiri Benc
2018-01-18 20:45 ` William Tu
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=1516210371-20732-1-git-send-email-u9012063@gmail.com \
--to=u9012063@gmail.com \
--cc=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.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).