[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171009.101828.1483628850783668385.davem@davemloft.net>
Date: Mon, 09 Oct 2017 10:18:28 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, yotamg@...lanox.com, idosch@...lanox.com,
nogahf@...lanox.com, mlxsw@...lanox.com, ivecera@...hat.com,
nikolay@...ulusnetworks.com, andrew@...n.ch,
stephen@...workplumber.org, nbd@....name, roopa@...ulusnetworks.com
Subject: Re: [patch net-next v2 0/5] mlxsw: Offload bridge device mrouter
From: Jiri Pirko <jiri@...nulli.us>
Date: Mon, 9 Oct 2017 11:15:30 +0200
> From: Jiri Pirko <jiri@...lanox.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.
Powered by blists - more mailing lists