From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
Ian May <ianm@nvidia.com>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] sched_ext: idle: Introduce node-aware idle cpu kfunc helpers
Date: Sat, 8 Feb 2025 10:19:38 +0100 [thread overview]
Message-ID: <Z6chqn0Xf6xhL5gA@gpd3> (raw)
In-Reply-To: <Z6aLvYaYlQ3KRZQM@slm.duckdns.org>
On Fri, Feb 07, 2025 at 12:39:57PM -1000, Tejun Heo wrote:
> Hello,
>
> On Fri, Feb 07, 2025 at 09:40:53PM +0100, Andrea Righi wrote:
> > +/**
> > + * scx_bpf_cpu_to_node - Return the NUMA node the given @cpu belongs to
> > + */
> > +__bpf_kfunc int scx_bpf_cpu_to_node(s32 cpu)
>
> Maybe scx_bpf_cpu_node() to be in line with scx_bpf_task_cpu/cgroup()?
Ok, then maybe we can have scx_bpf_cpu_node() for the kfunc, that wraps
scx_cpu_node() for internal use.
>
> > +{
> > +#ifdef CONFIG_NUMA
> > + if (cpu < 0 || cpu >= nr_cpu_ids)
> > + return -EINVAL;
>
> Use ops_cpu_valid()? Otherwise, we can end up calling cpu_to_node() with an
> impossible CPU. Also, I don't think CPU -> node mapping function should be
> able to return an error value. It should just trigger ops error.
Ok.
>
> > +
> > + return idle_cpu_to_node(cpu);
>
> This is contingent on scx_builtin_idle_per_node, right? It's confusing for
> CPU -> node mapping function to return NUMA_NO_NODE depending on an ops
> flag. Shouldn't this be a generic mapping function?
The idea is that BPF schedulers can use this kfunc to determine the right
idle cpumask to use, for example a typical usage could be:
int node = scx_bpf_cpu_node(prev_cpu);
s32 cpu = scx_bpf_pick_idle_cpu_in_node(p->cpus_ptr, node, SCX_PICK_IDLE_IN_NODE);
Or:
int node = scx_bpf_cpu_node(prev_cpu);
const struct cpumask *idle_cpumask = scx_bpf_get_idle_cpumask_node(node);
When SCX_OPS_BUILTIN_IDLE_PER_NODE is disabled, we need to point to the
global idle cpumask, that is identified by NUMA_NO_NODE, so this is why we
can return NUMA_NO_NODE fro scx_bpf_cpu_node().
Do you think we should make this more clear / document this better. Or do
you think we should use a different API?
>
> > index 50e1499ae0935..caa1a80f9a60c 100644
> > --- a/tools/sched_ext/include/scx/compat.bpf.h
> > +++ b/tools/sched_ext/include/scx/compat.bpf.h
> > @@ -130,6 +130,25 @@ bool scx_bpf_dispatch_vtime_from_dsq___compat(struct bpf_iter_scx_dsq *it__iter,
> > scx_bpf_now() : \
> > bpf_ktime_get_ns())
> >
> > +#define __COMPAT_scx_bpf_cpu_to_node(cpu) \
> > + (bpf_ksym_exists(scx_bpf_cpu_to_node) ? \
> > + scx_bpf_cpu_to_node(cpu) : 0)
> > +
> > +#define __COMPAT_scx_bpf_get_idle_cpumask_node(node) \
> > + (bpf_ksym_exists(scx_bpf_get_idle_cpumask_node) ? \
> > + scx_bpf_get_idle_cpumask_node(node) : \
> > + scx_bpf_get_idle_cpumask()) \
> > +
> > +#define __COMPAT_scx_bpf_get_idle_smtmask_node(node) \
> > + (bpf_ksym_exists(scx_bpf_get_idle_smtmask_node) ? \
> > + scx_bpf_get_idle_smtmask_node(node) : \
> > + scx_bpf_get_idle_smtmask())
> > +
> > +#define __COMPAT_scx_bpf_pick_idle_cpu_node(cpus_allowed, node, flags) \
> > + (bpf_ksym_exists(scx_bpf_pick_idle_cpu_node) ? \
> > + scx_bpf_pick_idle_cpu_node(cpus_allowed, node, flags) : \
> > + scx_bpf_pick_idle_cpu(cpus_allowed, flags))
>
> Can you please document when these compat macros can be dropped? Also,
> shouldn't it also provide a compat macro for the new ops flag using
> __COMPAT_ENUM_OR_ZERO()? Otherwise, trying to load new binary using the new
> flag on an older kernel will fail, right?
Right. Will add that.
Thanks,
-Andrea
next prev parent reply other threads:[~2025-02-08 9:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 20:40 [PATCHSET v10 sched_ext/for-6.15] sched_ext: split global idle cpumask into per-NUMA cpumasks Andrea Righi
2025-02-07 20:40 ` [PATCH 1/6] mm/numa: Introduce numa_nearest_nodemask() Andrea Righi
2025-02-09 17:40 ` Yury Norov
2025-02-10 8:28 ` Andrea Righi
2025-02-10 16:41 ` Yury Norov
2025-02-10 16:51 ` Andrea Righi
2025-02-07 20:40 ` [PATCH 2/6] sched/topology: Introduce for_each_numa_node() iterator Andrea Righi
2025-02-07 21:46 ` Tejun Heo
2025-02-07 21:55 ` Andrea Righi
2025-02-07 21:56 ` Tejun Heo
2025-02-09 17:51 ` Yury Norov
2025-02-09 17:50 ` Yury Norov
2025-02-07 20:40 ` [PATCH 3/6] sched_ext: idle: Introduce SCX_OPS_BUILTIN_IDLE_PER_NODE Andrea Righi
2025-02-07 20:40 ` [PATCH 4/6] sched_ext: idle: introduce SCX_PICK_IDLE_IN_NODE Andrea Righi
2025-02-07 22:02 ` Tejun Heo
2025-02-07 20:40 ` [PATCH 5/6] sched_ext: idle: Per-node idle cpumasks Andrea Righi
2025-02-07 22:30 ` Tejun Heo
2025-02-08 8:47 ` Andrea Righi
2025-02-09 18:07 ` Yury Norov
2025-02-10 16:57 ` Yury Norov
2025-02-11 7:32 ` Andrea Righi
2025-02-11 7:41 ` Andrea Righi
2025-02-11 9:50 ` Andrea Righi
2025-02-11 14:19 ` Yury Norov
2025-02-11 14:34 ` Andrea Righi
2025-02-11 14:45 ` Andrea Righi
2025-02-11 16:38 ` Steven Rostedt
2025-02-11 18:05 ` Andrea Righi
2025-02-07 20:40 ` [PATCH 6/6] sched_ext: idle: Introduce node-aware idle cpu kfunc helpers Andrea Righi
2025-02-07 22:39 ` Tejun Heo
2025-02-08 9:19 ` Andrea Righi [this message]
2025-02-09 6:31 ` Tejun Heo
2025-02-09 8:11 ` Andrea Righi
2025-02-10 6:01 ` Tejun Heo
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=Z6chqn0Xf6xhL5gA@gpd3 \
--to=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=ianm@nvidia.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.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