[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9a61559-e7f7-86e9-6ac2-c988255db5f0@gmail.com>
Date: Tue, 10 Aug 2021 02:43:46 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: DENG Qingfang <dqfext@...il.com>, Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
David Miller <davem@...emloft.net>,
Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>,
bridge@...ts.linux-foundation.org, netdev <netdev@...r.kernel.org>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>
Subject: Re: Bridge port isolation offload
On 8/9/2021 9:40 PM, DENG Qingfang wrote:
> Hi,
>
> Bridge port isolation flag (BR_ISOLATED) was added in commit
> 7d850abd5f4e. But switchdev does not offload it currently.
> It should be easy to implement in drivers, just like bridge offload
> but prevent isolated ports to communicate with each other.
>
> Your thoughts?
It maps well on Broadcom switches but there was not a known use case
AFAICT that warranted mapping this flag to program the switch hardware
accordingly.
--
Florian
Powered by blists - more mailing lists