From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org
Cc: ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] sfc: optimize RXQs count and affinities
Date: Wed, 02 Mar 2022 01:40:09 +0000 [thread overview]
Message-ID: <164618520999.21891.9258441569559448008.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220228132254.25787-1-ihuguet@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2022-03-02 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:22 [PATCH v2 net-next 0/2] sfc: optimize RXQs count and affinities Íñigo Huguet
2022-02-28 13:22 ` [PATCH v2 net-next 1/2] sfc: default config to 1 channel/core in local NUMA node only Íñigo Huguet
2022-03-01 9:16 ` Martin Habets
2022-02-28 13:22 ` [PATCH v2 net-next 2/2] sfc: set affinity hints " Íñigo Huguet
2022-03-01 9:16 ` Martin Habets
2022-03-02 1:40 ` patchwork-bot+netdevbpf [this message]
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=164618520999.21891.9258441569559448008.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?w43DsWlnbyBIdWd1ZXQgPGlodWd1ZXRAcmVkaGF0LmNvbT4=?=@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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).