Thread (6 messages) 6 messages, 3 authors, 2022-03-02

Re: [PATCH v2 net-next 0/2] sfc: optimize RXQs count and affinities

From: patchwork-bot+netdevbpf@kernel.org
Date: 2022-03-02 01:40:16

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski [off-list ref]:

On Mon, 28 Feb 2022 14:22:52 +0100 you wrote:
In sfc driver one RX queue per physical core was allocated by default.
Later on, IRQ affinities were set spreading the IRQs in all NUMA local
CPUs.

However, with that default configuration it result in a non very optimal
configuration in many modern systems. Specifically, in systems with hyper
threading and 2 NUMA nodes, affinities are set in a way that IRQs are
handled by all logical cores of one same NUMA node. Handling IRQs from
both hyper threading siblings has no benefit, and setting affinities to one
queue per physical core is neither a very good idea because there is a
performance penalty for moving data across nodes (I was able to check it
with some XDP tests using pktgen).

[...]
Here is the summary with links:
  - [v2,net-next,1/2] sfc: default config to 1 channel/core in local NUMA node only
    (no matching commit)
  - [v2,net-next,2/2] sfc: set affinity hints in local NUMA node only
    https://git.kernel.org/netdev/net-next/c/09a99ab16c60

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help