[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <417c677f-268a-4163-b07e-deea8f9b9b40@intel.com>
Date: Wed, 22 Oct 2025 16:46:00 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: I Viswanath <viswanathiyyappan@...il.com>, <davem@...emloft.net>,
<edumazet@...gle.com>, <kuba@...nel.org>, <pabeni@...hat.com>,
<horms@...nel.org>, <sdf@...ichev.me>, <kuniyu@...gle.com>,
<ahmed.zaki@...el.com>, <aleksander.lobakin@...el.com>,
<andrew+netdev@...n.ch>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<skhan@...uxfoundation.org>, <linux-kernel-mentees@...ts.linux.dev>,
<david.hunter.linux@...il.com>, <khalid@...nel.org>
Subject: Re: [RFC net-next PATCH 0/2] net: Split ndo_set_rx_mode into snapshot
and deferred write
On 10/20/2025 6:48 AM, I Viswanath wrote:
> 3. All calls to modify rx_mode should pass through the set_rx_mode +
> schedule write_rx_config execution flow.
>
> 1 and 2 are guaranteed because of the properties of work queues
>
> Drivers need to ensure 3
>
Is there any mechanism to make this guarantee either implemented or at
least verified by the core? If not that, what about some sort of way to
lint driver code and make sure its correct?
In my experience, requiring drivers to do something right typically
results in a long tail of correcting drivers into the future..
Download attachment "OpenPGP_signature.asc" of type "application/pgp-signature" (237 bytes)
Powered by blists - more mailing lists