[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190801142252.pdzd6knl2ytuty7h@lx-anielsen.microsemi.net>
Date: Thu, 1 Aug 2019 16:22:53 +0200
From: "Allan W. Nielsen" <allan.nielsen@...rochip.com>
To: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
CC: Horatiu Vultur <horatiu.vultur@...rochip.com>,
<roopa@...ulusnetworks.com>, <davem@...emloft.net>,
<bridge@...ts.linux-foundation.org>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: bridge: Allow bridge to joing multicast groups
The 07/26/2019 15:31, Nikolay Aleksandrov wrote:
...
> You know that in order to not run in promisc mode you'll have to disable
> port flooding and port learning, right ? Otherwise they're always put in promisc.
Yes, we have spend some time looking at nbp_update_port_count and trying to
understand the reasoning behind it.
Our understanding is that this is to make it work with a pure SW bridge
implementation, and this is actually an optimization to allow disable promisc
mode if all forwarding is static (no flooding and no learning).
We also noticed that the Ocelot and the Rocker drivers avoids this "issue" by
not implementing promisc mode.
But promisc mode is a really nice feature for debugging, and we would actually
like to have it, and when HW that can do learning/flooding it does not seem to
be necessary.
I tried to understand how this is handled in the Mellanox drivers, but gave up.
Too big, and we lack the insight in their design.
Do you know if there are better ways to prevent switchdev-offloaded-slave
interfaces to go to promisc mode?
/Allan
Powered by blists - more mailing lists