[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <164618520999.21891.9258441569559448008.git-patchwork-notify@kernel.org>
Date: Wed, 02 Mar 2022 01:40:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Íñigo Huguet <ihuguet@...hat.com>@ci.codeaurora.org
Cc: ecree.xilinx@...il.com, habetsm.xilinx@...il.com,
davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] sfc: optimize RXQs count and affinities
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
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
Powered by blists - more mailing lists