[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241029121619.1a710601@kernel.org>
Date: Tue, 29 Oct 2024 12:16:19 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Petr Machata <petrm@...dia.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
<netdev@...r.kernel.org>, Ido Schimmel <idosch@...dia.com>, "Amit Cohen"
<amcohen@...dia.com>, Vladimir Oltean <vladimir.oltean@....com>,
<mlxsw@...dia.com>
Subject: Re: [PATCH net-next 0/8] net: Shift responsibility for FDB
notifications to drivers
On Tue, 22 Oct 2024 16:50:11 +0200 Petr Machata wrote:
> Besides this approach, we considered just passing a boolean back from the
> driver, which would indicate whether the notification was done. But the
> approach presented here seems cleaner.
What about adding a bit to the ops struct to indicate that
the driver will generate the notification? Seems smaller in
terms of LoC and shifts the responsibility of doing extra
work towards more complex users.
Powered by blists - more mailing lists