[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241219194237.31822cba@kernel.org>
Date: Thu, 19 Dec 2024 19:42:37 -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 Wed, 18 Dec 2024 09:58:39 -0700 Ahmed Zaki wrote:
> + if (!glue_created && flags & NAPIF_IRQ_AFFINITY) {
> + glue = kzalloc(sizeof(*glue), GFP_KERNEL);
> + if (!glue)
> + return;
> + glue->notify.notify = netif_irq_cpu_rmap_notify;
> + glue->notify.release = netif_napi_affinity_release;
> + glue->data = napi;
> + glue->rmap = NULL;
> + napi->irq_flags |= NAPIF_IRQ_NORMAP;
Why allocate the glue? is it not possible to add the fields:
struct irq_affinity_notify notify;
u16 index;
to struct napi_struct ?
Powered by blists - more mailing lists