From: patchwork-bot+netdevbpf@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, kuba@kernel.org,
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
Subject: Re: [Intel-wired-lan] [PATCH net-next v9 0/6] net: napi: add CPU affinity to napi->config
Date: Thu, 27 Feb 2025 04:10:32 +0000 [thread overview]
Message-ID: <174062943228.962704.4253431175547388927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224232228.990783-1-ahmed.zaki@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Feb 2025 16:22:21 -0700 you wrote:
> Drivers usually need to re-apply the user-set IRQ affinity to their IRQs
> after reset. However, since there can be only one IRQ affinity notifier
> for each IRQ, registering IRQ notifiers conflicts with the ARFS rmap
> management in the core (which also registers separate IRQ affinity
> notifiers).
>
> Move the IRQ affinity management to the napi struct. This way we can have
> a unified IRQ notifier to re-apply the user-set affinity and also manage
> the ARFS rmaps.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/6] net: move aRFS rmap management and CPU affinity to core
https://git.kernel.org/netdev/net-next/c/bd7c00605ee0
- [net-next,v9,2/6] net: ena: use napi's aRFS rmap notifers
https://git.kernel.org/netdev/net-next/c/de340d8206bf
- [net-next,v9,3/6] ice: clear NAPI's IRQ numbers in ice_vsi_clear_napi_queues()
https://git.kernel.org/netdev/net-next/c/30b78ba3d4fe
- [net-next,v9,4/6] ice: use napi's irq affinity and rmap IRQ notifiers
https://git.kernel.org/netdev/net-next/c/4063af296762
- [net-next,v9,5/6] idpf: use napi's irq affinity
https://git.kernel.org/netdev/net-next/c/deab38f8f011
- [net-next,v9,6/6] selftests: drv-net: add tests for napi IRQ affinity notifiers
https://git.kernel.org/netdev/net-next/c/185646a8a0a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@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, kuba@kernel.org,
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
Subject: Re: [PATCH net-next v9 0/6] net: napi: add CPU affinity to napi->config
Date: Thu, 27 Feb 2025 04:10:32 +0000 [thread overview]
Message-ID: <174062943228.962704.4253431175547388927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224232228.990783-1-ahmed.zaki@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Feb 2025 16:22:21 -0700 you wrote:
> Drivers usually need to re-apply the user-set IRQ affinity to their IRQs
> after reset. However, since there can be only one IRQ affinity notifier
> for each IRQ, registering IRQ notifiers conflicts with the ARFS rmap
> management in the core (which also registers separate IRQ affinity
> notifiers).
>
> Move the IRQ affinity management to the napi struct. This way we can have
> a unified IRQ notifier to re-apply the user-set affinity and also manage
> the ARFS rmaps.
>
> [...]
Here is the summary with links:
- [net-next,v9,1/6] net: move aRFS rmap management and CPU affinity to core
https://git.kernel.org/netdev/net-next/c/bd7c00605ee0
- [net-next,v9,2/6] net: ena: use napi's aRFS rmap notifers
https://git.kernel.org/netdev/net-next/c/de340d8206bf
- [net-next,v9,3/6] ice: clear NAPI's IRQ numbers in ice_vsi_clear_napi_queues()
https://git.kernel.org/netdev/net-next/c/30b78ba3d4fe
- [net-next,v9,4/6] ice: use napi's irq affinity and rmap IRQ notifiers
https://git.kernel.org/netdev/net-next/c/4063af296762
- [net-next,v9,5/6] idpf: use napi's irq affinity
https://git.kernel.org/netdev/net-next/c/deab38f8f011
- [net-next,v9,6/6] selftests: drv-net: add tests for napi IRQ affinity notifiers
https://git.kernel.org/netdev/net-next/c/185646a8a0a8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-27 4:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 23:22 [Intel-wired-lan] [PATCH net-next v9 0/6] net: napi: add CPU affinity to napi->config Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 1/6] net: move aRFS rmap management and CPU affinity to core Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 2/6] net: ena: use napi's aRFS rmap notifers Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-03-03 17:11 ` [Intel-wired-lan] " Arinzon, David
2025-03-03 17:11 ` Arinzon, David
2025-03-03 18:03 ` [Intel-wired-lan] " Ahmed Zaki
2025-03-04 22:37 ` Ahmed Zaki
2025-03-05 6:33 ` Arinzon, David
2025-03-05 6:33 ` Arinzon, David
2025-03-05 14:00 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 3/6] ice: clear NAPI's IRQ numbers in ice_vsi_clear_napi_queues() Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 4/6] ice: use napi's irq affinity and rmap IRQ notifiers Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 5/6] idpf: use napi's irq affinity Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-24 23:22 ` [Intel-wired-lan] [PATCH net-next v9 6/6] selftests: drv-net: add tests for napi IRQ affinity notifiers Ahmed Zaki
2025-02-24 23:22 ` Ahmed Zaki
2025-02-27 4:10 ` patchwork-bot+netdevbpf [this message]
2025-02-27 4:10 ` [PATCH net-next v9 0/6] net: napi: add CPU affinity to napi->config patchwork-bot+netdevbpf
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=174062943228.962704.4253431175547388927.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--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.