mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
	Yury Norov <yury.norov@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] sched_ext: Introduce per-NUMA idle cpumasks
Date: Wed, 4 Dec 2024 08:53:15 -1000	[thread overview]
Message-ID: <Z1ClG6qOvesfyGSU@slm.duckdns.org> (raw)
In-Reply-To: <Z1AVx-yUY_37uMCb@gpd3>

Hello,

On Wed, Dec 04, 2024 at 09:41:43AM +0100, Andrea Righi wrote:
...
> I like the idea of introducing a flag. The default should be flattened
> cpumask, so everything remains the same, and if a scheduler explicitly
> enables SCX_OPS_NUMA_IDLE_MASK (suggestions for the name?) we can switch
> to the NUMA-aware idle logic.

I think it generally works better to use "node" instead of "numa" for these
interfaces. That's more common and matches the interface functions that need
to be used and exposed, so maybe sth like SCX_OPS_BUILTIN_IDLE_PER_NODE or
SCX_OPS_NODE_BUILTIN_IDLE?

Thanks.

-- 
tejun

  reply	other threads:[~2024-12-04 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 15:36 [PATCHSET v3 sched_ext/for-6.13] sched_ext: split global idle cpumask into per-NUMA cpumasks Andrea Righi
2024-12-03 15:36 ` [PATCH 1/3] nodemask: Introduce for_each_node_mask_wrap/for_each_node_state_wrap() Andrea Righi
2024-12-03 16:27   ` Yury Norov
2024-12-03 15:36 ` [PATCH 2/3] sched_ext: Introduce per-NUMA idle cpumasks Andrea Righi
2024-12-04  0:04   ` Tejun Heo
2024-12-04  0:38     ` Yury Norov
2024-12-04  8:47       ` Andrea Righi
2024-12-04  8:41     ` Andrea Righi
2024-12-04 18:53       ` Tejun Heo [this message]
2024-12-03 15:36 ` [PATCH 3/3] sched_ext: get rid of the scx_selcpu_topo_numa logic Andrea Righi

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=Z1ClG6qOvesfyGSU@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=void@manifault.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
all inboxes | Powered by JetHome®