[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87d8a49c-41e3-4b18-9ada-cb64fa66fe9b@blackwall.org>
Date: Mon, 25 Nov 2024 00:01:11 +0200
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Elliot Ayrey <Elliot.Ayrey@...iedtelesis.co.nz>,
"andrew@...n.ch" <andrew@...n.ch>, "olteanv@...il.com" <olteanv@...il.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"pabeni@...hat.com" <pabeni@...hat.com>, "roopa@...dia.com"
<roopa@...dia.com>, "edumazet@...gle.com" <edumazet@...gle.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"horms@...nel.org" <horms@...nel.org>, "kuba@...nel.org" <kuba@...nel.org>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"bridge@...ts.linux.dev" <bridge@...ts.linux.dev>
Subject: Re: [RFC net-next (resend) 1/4] net: bridge: respect sticky flag on
external learn
On 24/11/2024 23:01, Elliot Ayrey wrote:
> On Sat, 2024-11-09 at 15:32 +0200, Nikolay Aleksandrov wrote:
>> So you have a sticky fdb entry added, but it is still allowed to roam
>> in HW?
>
> No the hardware has informed us a host has _tried_ to roam.
>
> As I think about this more, using the sticky bit alone probably isn't
> the best idea and it might be better if this mechanism were related to
> a port being locked? After all the port being locked in hardware is
> what generates this event.
That does sound better, but we should have the same functionality
in software as well. Perhaps optional to avoid potential flood of
current users with unexpected notifications, see my response to
the other mail for more info.
Cheers,
Nik
Powered by blists - more mailing lists