From: Tariq Toukan <tariqt@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>
Cc: Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
Gal Pressman <gal@nvidia.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
<linux-kernel@vger.kernel.org>, Tariq Toukan <tariqt@nvidia.com>
Subject: [PATCH net-next 0/2] mlx5: Use NUMA distance metrics
Date: Sun, 17 Jul 2022 08:22:59 +0300 [thread overview]
Message-ID: <20220717052301.19067-1-tariqt@nvidia.com> (raw)
Hi,
Expose the scheduler's sched_numa_find_closest() function, and use it in
mlx5 device driver. This replaces the binary NUMA preference (local /
remote) with an improved one that minds the actual distances, so that
remote NUMAs with short distance are preferred over farther ones.
This has significant performance implications when using NUMA-aware
memory allocations, improving the throughput and CPU utilization.
Regards,
Tariq
Tariq Toukan (2):
sched/topology: Expose sched_numa_find_closest
net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity
hints
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 46 ++++++++++++++++++--
include/linux/sched/topology.h | 2 +
kernel/sched/topology.c | 1 +
3 files changed, 46 insertions(+), 3 deletions(-)
--
2.21.0
next reply other threads:[~2022-07-17 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 5:22 Tariq Toukan [this message]
2022-07-17 5:23 ` [PATCH net-next 1/2] sched/topology: Expose sched_numa_find_closest Tariq Toukan
2022-07-18 10:19 ` Peter Zijlstra
2022-07-18 11:42 ` Tariq Toukan
2022-07-17 5:23 ` [PATCH net-next 2/2] net/mlx5: Improve remote NUMA preferences used for the IRQ affinity hints Tariq Toukan
2022-07-17 21:51 ` Saeed Mahameed
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=20220717052301.19067-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=saeedm@nvidia.com \
--cc=vincent.guittot@linaro.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).