3 messages, 3 authors, 2021-08-10 · open the first message on its own page
From: DENG Qingfang <dqfext@gmail.com>
Date: 2021-08-10 04:41:04
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? Regards, Qingfang
From: Florian Fainelli <f.fainelli@gmail.com>
Date: 2021-08-10 09:43:58
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
From: Vladimir Oltean <olteanv@gmail.com>
Date: 2021-08-10 10:42:57
On Tue, Aug 10, 2021 at 12:40:49PM +0800, 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?
If nothing else, do add BR_ISOLATED to BR_PORT_FLAGS_HW_OFFLOAD so that switchdev drivers which have an offloaded data plane have a chance to reject this new bridge port flag if they don't support it yet.