From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: Joe Damato <jdamato@fastly.com>, <netdev@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>, <andrew+netdev@lunn.ch>,
<edumazet@google.com>, <horms@kernel.org>, <pabeni@redhat.com>,
<davem@davemloft.net>, <michael.chan@broadcom.com>,
<tariqt@nvidia.com>, <anthony.l.nguyen@intel.com>,
<przemyslaw.kitszel@intel.com>, <shayd@nvidia.com>,
<akpm@linux-foundation.org>, <shayagr@amazon.com>,
<kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [PATCH net-next v7 2/5] net: napi: add CPU affinity to napi_config
Date: Thu, 6 Feb 2025 18:33:52 -0800 [thread overview]
Message-ID: <20250206183352.4cecc85e@kernel.org> (raw)
In-Reply-To: <8270a43c-61f8-446d-8701-4fbd13a72e32@intel.com>
On Wed, 5 Feb 2025 08:20:20 -0700 Ahmed Zaki wrote:
> >> + if (napi->dev->rx_cpu_rmap_auto) {
> >> rc = napi_irq_cpu_rmap_add(napi, irq);
> >> if (rc)
> >> netdev_warn(napi->dev, "Unable to update ARFS map (%d)\n",
> >> rc);
> >> + } else if (napi->config && napi->dev->irq_affinity_auto) {
> >> + napi->notify.notify = netif_napi_irq_notify;
> >> + napi->notify.release = netif_napi_affinity_release;
> >> +
> >> + rc = irq_set_affinity_notifier(irq, &napi->notify);
> >> + if (rc)
> >> + netdev_warn(napi->dev, "Unable to set IRQ notifier (%d)\n",
> >> + rc);
> >> }
> >
> > Should there be a WARN_ON or WARN_ON_ONCE in here somewhere if the
> > driver calls netif_napi_set_irq_locked but did not link NAPI config
> > with a call to netif_napi_add_config?
> >
> > It seems like in that case the driver is buggy and a warning might
> > be helpful.
> >
>
> I think that is a good idea, if there is a new version I can add this in
> the second part of the if:
>
>
> if (WARN_ON_ONCE(!napi->config))
> return;
To be clear, this will make it illegal to set IRQ on a NAPI instance
before it's listed. Probably for the best if we also have auto-remove
in netif_napi_del().
next prev parent reply other threads:[~2025-02-07 2:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 22:06 [PATCH net-next v7 0/5] net: napi: add CPU affinity to napi->config Ahmed Zaki
2025-02-04 22:06 ` [PATCH net-next v7 1/5] net: move ARFS rmap management to core Ahmed Zaki
2025-02-07 2:29 ` Jakub Kicinski
2025-02-10 15:04 ` Ahmed Zaki
2025-02-11 0:13 ` Jakub Kicinski
2025-02-04 22:06 ` [PATCH net-next v7 2/5] net: napi: add CPU affinity to napi_config Ahmed Zaki
2025-02-04 22:43 ` Joe Damato
2025-02-05 15:20 ` Ahmed Zaki
2025-02-07 2:33 ` Jakub Kicinski [this message]
2025-02-07 2:37 ` Jakub Kicinski
2025-02-04 22:06 ` [PATCH net-next v7 3/5] bnxt: use napi's irq affinity Ahmed Zaki
2025-02-04 22:06 ` [PATCH net-next v7 4/5] ice: " Ahmed Zaki
2025-02-04 22:06 ` [PATCH net-next v7 5/5] idpf: " Ahmed Zaki
2025-02-07 0:24 ` [PATCH net-next v7 0/5] net: napi: add CPU affinity to napi->config Joe Damato
2025-02-07 18:47 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250206183352.4cecc85e@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jdamato@fastly.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shayagr@amazon.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).