From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, arkadis@mellanox.com,
idosch@mellanox.com, mlxsw@mellanox.com
Subject: Re: [patch net-next 0/4] mlxsw: Traps enhancements
Date: Mon, 17 Jul 2017 09:19:57 -0700 (PDT) [thread overview]
Message-ID: <20170717.091957.644800410884948370.davem@davemloft.net> (raw)
In-Reply-To: <20170717121532.4036-1-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Mon, 17 Jul 2017 14:15:28 +0200
> Ido says:
>
> The first patch makes sure the driver marks packets that were trapped
> in the router and might have already been flooded by the bridge, so that
> the bridge driver won't flood them again. This isn't critical at this time
> point, but will be when Neighbour Discovery traps are introduced as these
> are multicast packets that are trapped in the router.
>
> The second and third patches add new traps - for MLD and Router Alert
> packets. The last patch takes advantage of that and floods IPv6
> unregistered multicast packets only to mrouter ports instead of all ports.
Series applied, thanks.
prev parent reply other threads:[~2017-07-17 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 12:15 [patch net-next 0/4] mlxsw: Traps enhancements Jiri Pirko
2017-07-17 12:15 ` [patch net-next 1/4] mlxsw: spectrum: Mark packets trapped in router Jiri Pirko
2017-07-17 12:15 ` [patch net-next 2/4] mlxsw: spectrum: Trap IPv4 packets with Router Alert option Jiri Pirko
2017-07-17 12:15 ` [patch net-next 3/4] mlxsw: spectrum: Add support for IPv6 MLDv1/2 traps Jiri Pirko
2017-07-17 12:15 ` [patch net-next 4/4] mlxsw: spectrum: Improve IPv6 unregistered multicast flooding Jiri Pirko
2017-07-17 16:19 ` David Miller [this message]
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=20170717.091957.644800410884948370.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arkadis@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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).