From: Jacob Keller <jacob.e.keller@intel.com>
To: Yury Norov <yury.norov@gmail.com>, <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Barry Song <baohua@kernel.org>, "Ben Segall" <bsegall@google.com>,
haniel Bristot de Oliveira <bristot@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
"Gal Pressman" <gal@nvidia.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heiko Carstens <hca@linux.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Juri Lelli <juri.lelli@redhat.com>,
"Leon Romanovsky" <leonro@nvidia.com>,
Mel Gorman <mgorman@suse.de>,
"Peter Zijlstra" <peterz@infradead.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Saeed Mahameed <saeedm@nvidia.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
Tariq Toukan <tariqt@nvidia.com>,
"Tariq Toukan" <ttoukan.linux@gmail.com>,
Tony Luck <tony.luck@intel.com>,
"Valentin Schneider" <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Cc: <linux-crypto@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] cpumask: improve on cpumask_local_spread() locality
Date: Thu, 8 Dec 2022 10:45:18 -0800 [thread overview]
Message-ID: <4ba59b52-7549-aa9f-5fac-22ea42190727@intel.com> (raw)
In-Reply-To: <20221208183101.1162006-1-yury.norov@gmail.com>
On 12/8/2022 10:30 AM, Yury Norov wrote:
> cpumask_local_spread() currently checks local node for presence of i'th
> CPU, and then if it finds nothing makes a flat search among all non-local
> CPUs. We can do it better by checking CPUs per NUMA hops.
>
> This series is inspired by Tariq Toukan and Valentin Schneider's
> "net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity
> hints"
>
> https://patchwork.kernel.org/project/netdevbpf/patch/20220728191203.4055-3-tariqt@nvidia.com/
>
> According to their measurements, for mlx5e:
>
> Bottleneck in RX side is released, reached linerate (~1.8x speedup).
> ~30% less cpu util on TX.
>
> This patch makes cpumask_local_spread() traversing CPUs based on NUMA
> distance, just as well, and I expect comparable improvement for its
> users, as in case of mlx5e.
>
> I tested new behavior on my VM with the following NUMA configuration:
>
> root@debian:~# numactl -H
> available: 4 nodes (0-3)
> node 0 cpus: 0 1 2 3
> node 0 size: 3869 MB
> node 0 free: 3740 MB
> node 1 cpus: 4 5
> node 1 size: 1969 MB
> node 1 free: 1937 MB
> node 2 cpus: 6 7
> node 2 size: 1967 MB
> node 2 free: 1873 MB
> node 3 cpus: 8 9 10 11 12 13 14 15
> node 3 size: 7842 MB
> node 3 free: 7723 MB
> node distances:
> node 0 1 2 3
> 0: 10 50 30 70
> 1: 50 10 70 30
> 2: 30 70 10 50
> 3: 70 30 50 10
>
> And the cpumask_local_spread() for each node and offset traversing looks
> like this:
>
> node 0: 0 1 2 3 6 7 4 5 8 9 10 11 12 13 14 15
> node 1: 4 5 8 9 10 11 12 13 14 15 0 1 2 3 6 7
> node 2: 6 7 0 1 2 3 8 9 10 11 12 13 14 15 4 5
> node 3: 8 9 10 11 12 13 14 15 4 5 6 7 0 1 2 3
>
> v1: https://lore.kernel.org/lkml/20221111040027.621646-5-yury.norov@gmail.com/T/
> v2: https://lore.kernel.org/all/20221112190946.728270-3-yury.norov@gmail.com/T/
> v3:
> - fix typo in find_nth_and_andnot_bit();
> - add 5th patch that simplifies cpumask_local_spread();
> - address various coding style nits.
>
The whole series look reasonable to me!
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2022-12-08 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 18:30 [PATCH v3 0/5] cpumask: improve on cpumask_local_spread() locality Yury Norov
2022-12-08 18:30 ` [PATCH v3 1/5] lib/find: introduce find_nth_and_andnot_bit Yury Norov
2022-12-08 18:30 ` [PATCH v3 2/5] cpumask: introduce cpumask_nth_and_andnot Yury Norov
2022-12-08 18:30 ` [PATCH v3 3/5] sched: add sched_numa_find_nth_cpu() Yury Norov
2022-12-08 18:31 ` [PATCH v3 4/5] cpumask: improve on cpumask_local_spread() locality Yury Norov
2022-12-08 18:31 ` [PATCH v3 5/5] lib/cpumask: reorganize cpumask_local_spread() logic Yury Norov
2022-12-08 20:17 ` Peter Lafreniere
2022-12-08 20:41 ` Yury Norov
2022-12-08 20:57 ` Peter Lafreniere
2022-12-08 18:45 ` Jacob Keller [this message]
2022-12-08 20:22 ` [PATCH v3 0/5] cpumask: improve on cpumask_local_spread() locality Tariq Toukan
2022-12-08 20:51 ` Yury Norov
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=4ba59b52-7549-aa9f-5fac-22ea42190727@intel.com \
--to=jacob.e.keller@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baohua@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=gal@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=jesse.brandeburg@intel.com \
--cc=jgg@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=tony.luck@intel.com \
--cc=ttoukan.linux@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox