[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1516820776-7995-1-git-send-email-u9012063@gmail.com>
Date: Wed, 24 Jan 2018 11:06:14 -0800
From: William Tu <u9012063@...il.com>
To: netdev@...r.kernel.org
Cc: pshelar@....org
Subject: [PATCHv5 net-next 0/2] net: erspan: add support for openvswitch
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 | 2 +-
net/ipv4/ip_gre.c | 38 +++++-------
net/ipv6/ip6_gre.c | 36 ++++-------
net/openvswitch/flow_netlink.c | 90 ++++++++++++++++++++++++++-
5 files changed, 211 insertions(+), 82 deletions(-)
--
v4->v5
rather than passing individual members of erspan_metadata,
just pass the whole binary structure between kernel and userspace,
suggested by Pravin.
v3->v4
change from be32 to u32 for OVS_ERSPAN_OPT_IDX, suggested by Jiri Benc.
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
Powered by blists - more mailing lists