[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250207104748.27c7f96b@kernel.org>
Date: Fri, 7 Feb 2025 10:47:48 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Ahmed Zaki <ahmed.zaki@...el.com>
Cc: netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
andrew+netdev@...n.ch, edumazet@...gle.com, horms@...nel.org,
pabeni@...hat.com, davem@...emloft.net, michael.chan@...adcom.com,
tariqt@...dia.com, anthony.l.nguyen@...el.com,
przemyslaw.kitszel@...el.com, jdamato@...tly.com, shayd@...dia.com,
akpm@...ux-foundation.org, shayagr@...zon.com,
kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH net-next v7 0/5] net: napi: add CPU affinity to
napi->config
On Tue, 4 Feb 2025 15:06:17 -0700 Ahmed Zaki wrote:
> Drivers usually need to re-apply the user-set IRQ affinity to their IRQs
> after reset. However, since there can be only one IRQ affinity notifier
> for each IRQ, registering IRQ notifiers conflicts with the ARFS rmap
> management in the core (which also registers separate IRQ affinity
> notifiers).
>
> Move the IRQ affinity management to the napi struct. This way we can have
> a unified IRQ notifier to re-apply the user-set affinity and also manage
> the ARFS rmaps. The first patch moves the ARFS rmap management to CORE.
> The second patch adds the IRQ affinity mask to napi_config and re-applies
> the mask after reset. Patches 3-5 use the new API for bnxt, ice and idpf
> drivers.
Hi Ahmed!
I put together a selftest for maintaining the affinity:
https://github.com/kuba-moo/linux/commit/de7d2475750ac05b6e414d7e5201e354b05cf146
It depends on a couple of selftest infra patches (in that branch)
which I just posted to the list. But if you'd like you can use
it against your drivers.
Powered by blists - more mailing lists