From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, yotamg@mellanox.com, idosch@mellanox.com,
nogahf@mellanox.com, mlxsw@mellanox.com, ivecera@redhat.com,
nikolay@cumulusnetworks.com, andrew@lunn.ch,
stephen@networkplumber.org, nbd@nbd.name,
roopa@cumulusnetworks.com
Subject: Re: [patch net-next v2 0/5] mlxsw: Offload bridge device mrouter
Date: Mon, 09 Oct 2017 10:18:28 -0700 (PDT) [thread overview]
Message-ID: <20171009.101828.1483628850783668385.davem@davemloft.net> (raw)
In-Reply-To: <20171009091535.1315-1-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Mon, 9 Oct 2017 11:15:30 +0200
> From: Jiri Pirko <jiri@mellanox.com>
>
> Yotam says:
>
> Similarly to a bridged port, the bridge device itself can be configured by
> the user to be an mrouter port. In this case, all multicast traffic should
> be forwarded to it. Make the mlxsw Spectrum driver offload these directives
> to the Spectrum hardware.
>
> Patches 1 and 2 add a new switchdev notification for bridge device mrouter
> port status and make the bridge module notify about it.
>
> Patches 3-5 change the mlxsw Spectrum driver to handle these notifications
> by adding the Spectrum router port to the bridge MDB entries.
>
> ---
> v1->v2:
> - patch1:
> - Don't add the MDB_RTR_TYPE_TEMP state and use the timer_pending to
> distinguish between learning-on and learning-off states
Series applied, thank you.
prev parent reply other threads:[~2017-10-09 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 9:15 [patch net-next v2 0/5] mlxsw: Offload bridge device mrouter Jiri Pirko
2017-10-09 9:15 ` [patch net-next v2 1/5] net: bridge: Notify on bridge device mrouter state changes Jiri Pirko
2017-10-09 10:19 ` Ivan Vecera
2017-10-09 10:52 ` Nikolay Aleksandrov
2017-10-09 9:15 ` [patch net-next v2 2/5] net: bridge: Export bridge multicast router state Jiri Pirko
2017-10-09 10:19 ` Ivan Vecera
2017-10-09 9:15 ` [patch net-next v2 3/5] mlxsw: spectrum: router: Export the mlxsw_sp_router_port function Jiri Pirko
2017-10-09 9:15 ` [patch net-next v2 4/5] mlxsw: spectrum_switchdev: Add support for router port in SMID entries Jiri Pirko
2017-10-09 9:15 ` [patch net-next v2 5/5] mlxsw: spectrum_switchdev: Support bridge mrouter notifications Jiri Pirko
2017-10-09 17:18 ` 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=20171009.101828.1483628850783668385.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=nogahf@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=yotamg@mellanox.com \
/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).