From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Tariq Toukan <tariqt@nvidia.com>,
"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
Subject: Re: [PATCH net-next V3 0/3] Introduce and use NUMA distance metrics
Date: Sun, 24 Jul 2022 15:09:11 +0300 [thread overview]
Message-ID: <09038324-65ed-8529-2f6c-671a15a8fb84@gmail.com> (raw)
In-Reply-To: <20220719162339.23865-1-tariqt@nvidia.com>
On 7/19/2022 7:23 PM, Tariq Toukan wrote:
> Hi,
>
> Implement and expose CPU spread API based on the scheduler's
> sched_numa_find_closest(). Use it in mlx5 and enic device drivers. 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
>
> v3:
> - Introduce the logic as a common API instead of being mlx5 specific.
> - Add implementation to enic device driver.
> - Use non-atomic version of __cpumask_clear_cpu.
>
Comments on V2 were addressed.
Please let me now of any other comments on this V3.
prev parent reply other threads:[~2022-07-24 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:23 Tariq Toukan
2022-07-19 16:23 ` [PATCH net-next V3 1/3] sched/topology: Add NUMA-based CPUs spread API Tariq Toukan
2022-07-28 15:23 ` Jakub Kicinski
2022-07-19 16:23 ` [PATCH net-next V3 2/3] net/mlx5e: Improve remote NUMA preferences used for the IRQ affinity hints Tariq Toukan
2022-07-19 16:23 ` [PATCH net-next V3 3/3] enic: Use NUMA distances logic when setting " Tariq Toukan
2022-07-24 12:09 ` Tariq Toukan [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=09038324-65ed-8529-2f6c-671a15a8fb84@gmail.com \
--to=ttoukan.linux@gmail.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=tariqt@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
all inboxes | Powered by JetHome®