From: Roopa Prabhu <roopa@nvidia.com>
To: <dsahern@gmail.com>
Cc: <netdev@vger.kernel.org>, <stephen@networkplumber.org>,
<razor@blackwall.org>
Subject: [PATCH iproute2 net-next v2 0/3] support for vxlan vni filtering
Date: Sun, 8 May 2022 04:53:37 +0000 [thread overview]
Message-ID: <20220508045340.120653-1-roopa@nvidia.com> (raw)
This series adds bridge command to manage
recently added vnifilter on a collect metadata
vxlan (external) device. Also includes per vni stats
support.
examples:
$bridge vni add dev vxlan0 vni 400
$bridge vni add dev vxlan0 vni 200 group 239.1.1.101
$bridge vni del dev vxlan0 vni 400
$bridge vni show
$bridge -s vni show
Nikolay Aleksandrov (1):
bridge: vni: add support for stats dumping
Roopa Prabhu (2):
bridge: vxlan device vnifilter support
ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device
v2 : replace matches by strcmp in bridge/vni.c. v2 still uses matches
in iplink_vxlan.c to match the rest of the code
bridge/Makefile | 2 +-
bridge/br_common.h | 2 +
bridge/bridge.c | 1 +
bridge/monitor.c | 28 ++-
bridge/vni.c | 439 ++++++++++++++++++++++++++++++++++++++++++
include/libnetlink.h | 9 +
ip/iplink_vxlan.c | 23 ++-
lib/libnetlink.c | 20 ++
man/man8/bridge.8 | 77 +++++++-
man/man8/ip-link.8.in | 9 +
10 files changed, 606 insertions(+), 4 deletions(-)
create mode 100644 bridge/vni.c
--
2.25.1
next reply other threads:[~2022-05-08 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 4:53 Roopa Prabhu [this message]
2022-05-08 4:53 ` [PATCH iproute2 net-next v2 1/3] bridge: vxlan device vnifilter support Roopa Prabhu
2022-05-08 4:53 ` [PATCH iproute2 net-next v2 2/3] ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device Roopa Prabhu
2022-05-08 4:53 ` [PATCH iproute2 net-next v2 3/3] bridge: vni: add support for stats dumping Roopa Prabhu
2022-05-08 15:53 ` [PATCH iproute2 net-next v2 0/3] support for vxlan vni filtering David Ahern
2022-05-08 16:13 ` Roopa Prabhu
2022-05-08 16:00 ` patchwork-bot+netdevbpf
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=20220508045340.120653-1-roopa@nvidia.com \
--to=roopa@nvidia.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.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).