All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	David Arinzon <darinzon@amazon.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v7 1/5] net: move ARFS rmap management to core
Date: Mon, 10 Feb 2025 16:13:15 -0800	[thread overview]
Message-ID: <20250210161315.51d9b2a9@kernel.org> (raw)
In-Reply-To: <760e3977-9f83-431b-b29b-f8ad1609b462@intel.com>

On Mon, 10 Feb 2025 08:04:43 -0700 Ahmed Zaki wrote:
> On 2025-02-06 7:29 p.m., Jakub Kicinski wrote:
> 
> > Speaking of which, why do the auto-removal in napi_disable()
> > rather than netif_napi_del() ? We don't reinstall on napi_enable()
> > and doing a disable() + enable() is fairly common during driver
> > reconfig.
> >   
> 
> The patch does not re-install the notifiers in napi_add either, they are 
> installed in set_irq() :
> 
> napi_add_config()  -> napi_set_irq()  -> napi_enable()
> 
> so napi_disable or napi_del seemed both OK to me.
> 
> However, I moved notifier auto-removal to npi_del() and did some testing 
> on ice but it seems the driver does not delete napi on "ip link down" 
> and that generates warnings on free_irq(). It only disables the napis.
> 
> So is this a bug? Do we need to ask drivers to disable __and__ delete 
> napis before freeing the IRQs?
> 
> If not, then we have to keep notifier aut-removal in napi_diasable().

If the driver releases the IRQ but keeps the NAPI instance I would have
expected it to call:

	napi_set_irq(napi, -1);

before freeing the IRQ. Otherwise the NAPI instance will "point" to 
a freed IRQ.

WARNING: multiple messages have this Message-ID (diff)
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>,
	David Arinzon <darinzon@amazon.com>
Subject: Re: [PATCH net-next v7 1/5] net: move ARFS rmap management to core
Date: Mon, 10 Feb 2025 16:13:15 -0800	[thread overview]
Message-ID: <20250210161315.51d9b2a9@kernel.org> (raw)
In-Reply-To: <760e3977-9f83-431b-b29b-f8ad1609b462@intel.com>

On Mon, 10 Feb 2025 08:04:43 -0700 Ahmed Zaki wrote:
> On 2025-02-06 7:29 p.m., Jakub Kicinski wrote:
> 
> > Speaking of which, why do the auto-removal in napi_disable()
> > rather than netif_napi_del() ? We don't reinstall on napi_enable()
> > and doing a disable() + enable() is fairly common during driver
> > reconfig.
> >   
> 
> The patch does not re-install the notifiers in napi_add either, they are 
> installed in set_irq() :
> 
> napi_add_config()  -> napi_set_irq()  -> napi_enable()
> 
> so napi_disable or napi_del seemed both OK to me.
> 
> However, I moved notifier auto-removal to npi_del() and did some testing 
> on ice but it seems the driver does not delete napi on "ip link down" 
> and that generates warnings on free_irq(). It only disables the napis.
> 
> So is this a bug? Do we need to ask drivers to disable __and__ delete 
> napis before freeing the IRQs?
> 
> If not, then we have to keep notifier aut-removal in napi_diasable().

If the driver releases the IRQ but keeps the NAPI instance I would have
expected it to call:

	napi_set_irq(napi, -1);

before freeing the IRQ. Otherwise the NAPI instance will "point" to 
a freed IRQ.

  reply	other threads:[~2025-02-11  0:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 22:06 [Intel-wired-lan] [PATCH net-next v7 0/5] net: napi: add CPU affinity to napi->config Ahmed Zaki
2025-02-04 22:06 ` Ahmed Zaki
2025-02-04 22:06 ` [Intel-wired-lan] [PATCH net-next v7 1/5] net: move ARFS rmap management to core Ahmed Zaki
2025-02-04 22:06   ` Ahmed Zaki
2025-02-07  2:29   ` [Intel-wired-lan] " Jakub Kicinski
2025-02-07  2:29     ` Jakub Kicinski
2025-02-10 15:04     ` [Intel-wired-lan] " Ahmed Zaki
2025-02-10 15:04       ` Ahmed Zaki
2025-02-11  0:13       ` Jakub Kicinski [this message]
2025-02-11  0:13         ` Jakub Kicinski
2025-02-04 22:06 ` [Intel-wired-lan] [PATCH net-next v7 2/5] net: napi: add CPU affinity to napi_config Ahmed Zaki
2025-02-04 22:06   ` Ahmed Zaki
2025-02-04 22:43   ` [Intel-wired-lan] " Joe Damato
2025-02-04 22:43     ` Joe Damato
2025-02-05 15:20     ` [Intel-wired-lan] " Ahmed Zaki
2025-02-05 15:20       ` Ahmed Zaki
2025-02-07  2:33       ` [Intel-wired-lan] " Jakub Kicinski
2025-02-07  2:33         ` Jakub Kicinski
2025-02-07  2:37   ` [Intel-wired-lan] " Jakub Kicinski
2025-02-07  2:37     ` Jakub Kicinski
2025-02-04 22:06 ` [Intel-wired-lan] [PATCH net-next v7 3/5] bnxt: use napi's irq affinity Ahmed Zaki
2025-02-04 22:06   ` Ahmed Zaki
2025-02-04 22:06 ` [Intel-wired-lan] [PATCH net-next v7 4/5] ice: " Ahmed Zaki
2025-02-04 22:06   ` Ahmed Zaki
2025-02-04 22:06 ` [Intel-wired-lan] [PATCH net-next v7 5/5] idpf: " Ahmed Zaki
2025-02-04 22:06   ` Ahmed Zaki
2025-02-07  0:24 ` [Intel-wired-lan] [PATCH net-next v7 0/5] net: napi: add CPU affinity to napi->config Joe Damato
2025-02-07  0:24   ` Joe Damato
2025-02-07 18:47 ` [Intel-wired-lan] " Jakub Kicinski
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=20250210161315.51d9b2a9@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.