From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Valentin Schneider <vschneid@redhat.com>,
<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Yury Norov <yury.norov@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mel Gorman <mgorman@suse.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Barry Song <song.bao.hua@hisilicon.com>,
Heiko Carstens <hca@linux.ibm.com>,
Tony Luck <tony.luck@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"Gal Pressman" <gal@nvidia.com>, Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH v2 0/5] sched, net: NUMA-aware CPU spreading interface
Date: Thu, 18 Aug 2022 09:28:59 -0700 [thread overview]
Message-ID: <9b062b28-e6dd-3af1-da02-1bc511ed6939@intel.com> (raw)
In-Reply-To: <20220817175812.671843-1-vschneid@redhat.com>
On 8/17/2022 10:58 AM, Valentin Schneider wrote:
> Hi folks,
>
> Tariq pointed out in [1] that drivers allocating IRQ vectors would benefit
> from having smarter NUMA-awareness (cpumask_local_spread() doesn't quite cut
> it).
>
> The proposed interface involved an array of CPUs and a temporary cpumask, and
> being my difficult self what I'm proposing here is an interface that doesn't
> require any temporary storage other than some stack variables (at the cost of
> one wild macro).
>
> Patch 5/5 is just there to showcase how the thing would be used. If this doesn't
> get hated on, I'll let Tariq pick this up and push it with his networking driver
> changes (with actual changelogs).
I am interested in this work, but it seems that at least on lore and in
my inbox, patch 3,4,5 didn't show up.
next prev parent reply other threads:[~2022-08-18 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 17:58 [PATCH v2 0/5] sched, net: NUMA-aware CPU spreading interface Valentin Schneider
2022-08-17 17:58 ` [PATCH v2 1/5] bitops: Introduce find_next_andnot_bit() Valentin Schneider
2022-08-18 14:08 ` Steven Rostedt
2022-08-18 16:26 ` Valentin Schneider
2022-08-18 17:00 ` Steven Rostedt
2022-08-18 19:04 ` Andy Shevchenko
2022-08-19 10:34 ` Valentin Schneider
2022-08-19 12:42 ` Yury Norov
2022-08-17 17:58 ` [PATCH v2 2/5] cpumask: Introduce for_each_cpu_andnot() Valentin Schneider
2022-08-18 22:38 ` Yury Norov
2022-08-19 10:24 ` Valentin Schneider
2022-08-18 16:28 ` Jesse Brandeburg [this message]
2022-08-18 16:43 ` [PATCH v2 0/5] sched, net: NUMA-aware CPU spreading interface Valentin Schneider
2022-08-18 16:51 ` Valentin Schneider
2022-08-18 16:45 ` [PATCH v2 3/5] sched/topology: Introduce sched_numa_hop_mask() Valentin Schneider
2022-08-18 16:45 ` [PATCH v2 4/5] sched/topology: Introduce for_each_numa_hop_cpu() Valentin Schneider
2022-08-18 16:45 ` [PATCH v2 5/5] SHOWCASE: net/mlx5e: Leverage for_each_numa_hop_cpu() Valentin Schneider
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=9b062b28-e6dd-3af1-da02-1bc511ed6939@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dietmar.eggemann@arm.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=saeedm@nvidia.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tariqt@nvidia.com \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).