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 0/6] mlxsw: Offload bridge device mrouter
Date: Sat, 07 Oct 2017 21:42:36 +0100 (WEST) [thread overview]
Message-ID: <20171007.214236.828908395863095403.davem@davemloft.net> (raw)
In-Reply-To: <20171005103642.1414-1-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 5 Oct 2017 12:36:36 +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-3 add a new switchdev notification for bridge device mrouter
> port status and make the bridge module notify about it.
>
> Patches 4-6 change the mlxsw Spectrum driver to handle these notifications
> by adding the Spectrum router port to the bridge MDB entries.
It looks like Nikolay wants some feedback addressed for patch #1.
Thanks.
prev parent reply other threads:[~2017-10-07 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 10:36 [patch net-next 0/6] mlxsw: Offload bridge device mrouter Jiri Pirko
2017-10-05 10:36 ` [patch net-next 1/6] net: bridge: Use the MDB_RTR_TYPE_TEMP on bridge device too Jiri Pirko
2017-10-05 12:09 ` Nikolay Aleksandrov
2017-10-05 12:12 ` Nikolay Aleksandrov
2017-10-05 12:52 ` Nikolay Aleksandrov
2017-10-08 5:23 ` Yotam Gigi
2017-10-08 9:39 ` Nikolay Aleksandrov
2017-10-08 9:42 ` Nikolay Aleksandrov
2017-10-08 10:30 ` Yotam Gigi
2017-10-05 10:36 ` [patch net-next 2/6] net: bridge: Notify on bridge device mrouter state changes Jiri Pirko
2017-10-05 13:11 ` Nikolay Aleksandrov
2017-10-05 10:36 ` [patch net-next 3/6] net: bridge: Export bridge multicast router state Jiri Pirko
2017-10-05 13:09 ` Nikolay Aleksandrov
2017-10-05 10:36 ` [patch net-next 4/6] mlxsw: spectrum: router: Export the mlxsw_sp_router_port function Jiri Pirko
2017-10-05 10:36 ` [patch net-next 5/6] mlxsw: spectrum_switchdev: Add support for router port in SMID entries Jiri Pirko
2017-10-05 10:36 ` [patch net-next 6/6] mlxsw: spectrum_switchdev: Support bridge mrouter notifications Jiri Pirko
2017-10-07 20:42 ` 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=20171007.214236.828908395863095403.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).