[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241220125110.4f8d8e6b@kernel.org>
Date: Fri, 20 Dec 2024 12:51:10 -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>, <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>
Subject: Re: [PATCH net-next v2 4/8] net: napi: add CPU affinity to
napi->config
On Fri, 20 Dec 2024 13:14:48 -0700 Ahmed Zaki wrote:
> > Then you can probably register a single unified handler, and inside
> > that handler check if the device wanted to have rmap or just affinity?
>
> This is what is in this patch already, all drivers following new
> approach will have netif_irq_cpu_rmap_notify() as their IRQ notifier.
>
> IIUC, your goal is to have the notifier inside napi, not irq_glue. For
> this, we'll have to have our own version of irq_cpu_rmap_add() (for the
> above reason).
>
> sounds OK?
Yes.
Powered by blists - more mailing lists