From: David Ahern <dsahern@gmail.com>
To: Roopa Prabhu <roopa@nvidia.com>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org, razor@blackwall.org
Subject: Re: [PATCH iproute2 net-next 0/3] support for vxlan vni filtering
Date: Thu, 5 May 2022 20:26:04 -0700 [thread overview]
Message-ID: <9278f614-9994-362c-75ae-5a0fe009ef01@gmail.com> (raw)
In-Reply-To: <20220501001205.33782-1-roopa@nvidia.com>
On 4/30/22 5:12 PM, Roopa Prabhu wrote:
> 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
>
>
hey Roopa: sorry for the delay; traveling. The patches have a number of
new uses of matches(). We are not taking any more of those; please
convert to strcmp. The rest looks fine to me.
next prev parent reply other threads:[~2022-05-06 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 0:12 [PATCH iproute2 net-next 0/3] support for vxlan vni filtering Roopa Prabhu
2022-05-01 0:12 ` [PATCH iproute2 net-next 1/3] bridge: vxlan device vnifilter support Roopa Prabhu
2022-05-01 0:12 ` [PATCH iproute2 net-next 2/3] ip: iplink_vxlan: add support to set vnifiltering flag on vxlan device Roopa Prabhu
2022-05-01 0:12 ` [PATCH iproute2 net-next 3/3] bridge: vni: add support for stats dumping Roopa Prabhu
2022-05-06 3:26 ` David Ahern [this message]
2022-05-08 3:45 ` [PATCH iproute2 net-next 0/3] support for vxlan vni filtering Roopa Prabhu
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=9278f614-9994-362c-75ae-5a0fe009ef01@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--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).