From: Jakub Kicinski <kuba@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: 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,
jdamato@fastly.com, shayd@nvidia.com, akpm@linux-foundation.org,
shayagr@amazon.com, kalesh-anakkur.purayil@broadcom.com,
pavan.chebbi@broadcom.com, David Arinzon <darinzon@amazon.com>
Subject: Re: [PATCH net-next v8 2/6] net: move ARFS rmap management to core
Date: Sat, 15 Feb 2025 09:53:07 -0800 [thread overview]
Message-ID: <20250215095307.44063132@kernel.org> (raw)
In-Reply-To: <20250211210657.428439-3-ahmed.zaki@intel.com>
On Tue, 11 Feb 2025 14:06:53 -0700 Ahmed Zaki wrote:
> +static void netif_napi_affinity_release(struct kref *ref)
> +{
> + struct napi_struct *napi =
> + container_of(ref, struct napi_struct, notify.kref);
> + struct cpu_rmap *rmap = napi->dev->rx_cpu_rmap;
> +
We should only get here from our own cleanup path, otherwise locking
and state sync may be a concern:
netdev_assert_locked(dev);
WARN_ON(test_and_clear_bit(NAPI_STATE_HAS_NOTIFIER,
&napi->state));
> + rmap->obj[napi->napi_rmap_idx] = NULL;
> + napi->napi_rmap_idx = -1;
> + cpu_rmap_put(rmap);
> +}
> +
> +static int napi_irq_cpu_rmap_add(struct napi_struct *napi, int irq)
> +{
> + struct cpu_rmap *rmap = napi->dev->rx_cpu_rmap;
> + int rc;
> +
> + napi->notify.notify = netif_irq_cpu_rmap_notify;
> + napi->notify.release = netif_napi_affinity_release;
> + cpu_rmap_get(rmap);
> + rc = cpu_rmap_add(rmap, napi);
> + if (rc < 0)
> + goto err_add;
> +
> + napi->napi_rmap_idx = rc;
> + rc = irq_set_affinity_notifier(irq, &napi->notify);
> + if (rc)
> + goto err_set;
> +
> + set_bit(NAPI_STATE_HAS_NOTIFIER, &napi->state);
> + return 0;
some of this function is common with the code in
netif_napi_set_irq_locked()
under
} else if (napi->dev->irq_affinity_auto) {
could you refactor this to avoid the duplication
and make it clearer which parts differ?
> +err_set:
> + rmap->obj[napi->napi_rmap_idx] = NULL;
> + napi->napi_rmap_idx = -1;
> +err_add:
> + cpu_rmap_put(rmap);
> + return rc;
> +}
> +
> +int netif_enable_cpu_rmap(struct net_device *dev, unsigned int num_irqs)
> +{
> + if (dev->rx_cpu_rmap_auto)
> + return 0;
> +
> + dev->rx_cpu_rmap = alloc_irq_cpu_rmap(num_irqs);
> + if (!dev->rx_cpu_rmap)
> + return -ENOMEM;
> +
> + dev->rx_cpu_rmap_auto = true;
> + return 0;
> +}
> +EXPORT_SYMBOL(netif_enable_cpu_rmap);
> +
> +static void netif_del_cpu_rmap(struct net_device *dev)
> +{
> + struct cpu_rmap *rmap = dev->rx_cpu_rmap;
> +
> + if (!dev->rx_cpu_rmap_auto)
> + return;
> +
> + /* Free the rmap */
> + cpu_rmap_put(rmap);
> + dev->rx_cpu_rmap = NULL;
> + dev->rx_cpu_rmap_auto = false;
> +}
> +
> +#else
> +static int napi_irq_cpu_rmap_add(struct napi_struct *napi, int irq)
> +{
> + return 0;
> +}
> +
> +int netif_enable_cpu_rmap(struct net_device *dev, unsigned int num_irqs)
> +{
> + return 0;
> +}
> +EXPORT_SYMBOL(netif_enable_cpu_rmap);
> +
> +static void netif_del_cpu_rmap(struct net_device *dev)
> +{
> +}
> +#endif
> +
> +void netif_napi_set_irq_locked(struct napi_struct *napi, int irq)
> +{
> + int rc;
maybe netdev_assert_locked_or_invisible(napi->dev); ?
> + if (napi->irq == irq)
> + return;
> +
> + /* Remove existing rmap entries */
> + if (test_and_clear_bit(NAPI_STATE_HAS_NOTIFIER, &napi->state))
> + irq_set_affinity_notifier(napi->irq, NULL);
> +
> + napi->irq = irq;
> + if (irq < 0)
> + return;
> +
> + rc = napi_irq_cpu_rmap_add(napi, irq);
> + if (rc)
> + netdev_warn(napi->dev, "Unable to update aRFS map (%d)\n", rc);
> +}
> +EXPORT_SYMBOL(netif_napi_set_irq_locked);
> +
> static void napi_restore_config(struct napi_struct *n)
> {
> n->defer_hard_irqs = n->config->defer_hard_irqs;
next prev parent reply other threads:[~2025-02-15 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 21:06 [PATCH net-next v8 0/6] net: napi: add CPU affinity to napi->config Ahmed Zaki
2025-02-11 21:06 ` [PATCH net-next v8 1/6] ice: clear NAPI's IRQ numbers in ice_vsi_clear_napi_queues() Ahmed Zaki
2025-02-11 21:06 ` [PATCH net-next v8 2/6] net: move ARFS rmap management to core Ahmed Zaki
2025-02-15 17:53 ` Jakub Kicinski [this message]
2025-02-11 21:06 ` [PATCH net-next v8 3/6] net: napi: add CPU affinity to napi_config Ahmed Zaki
2025-02-13 12:26 ` Paolo Abeni
2025-02-13 15:45 ` Ahmed Zaki
2025-02-15 17:58 ` Jakub Kicinski
2025-02-11 21:06 ` [PATCH net-next v8 4/6] bnxt: use napi's irq affinity Ahmed Zaki
2025-02-11 21:06 ` [PATCH net-next v8 5/6] ice: " Ahmed Zaki
2025-02-11 21:06 ` [PATCH net-next v8 6/6] idpf: " Ahmed Zaki
2025-02-15 17:41 ` [PATCH net-next v8 0/6] net: napi: add CPU affinity to napi->config Jakub Kicinski
2025-02-15 17:43 ` 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=20250215095307.44063132@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=darinzon@amazon.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=pavan.chebbi@broadcom.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).