mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vladimir Vdovin" <deliran@verdict.gg>
To: "Andrea Righi" <arighi@nvidia.com>,
	"Vladimir Vdovin" <deliran@verdict.gg>
Cc: "Tejun Heo" <tj@kernel.org>, "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>,
	"K Prateek Nayak" <kprateek.nayak@amd.com>,
	"Hui Su" <sh_def@163.com>, <sched-ext@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] sched_ext: Drive the NUMA balancing scan for SCX tasks
Date: Fri, 02 Oct 2026 18:08:25 +0300	[thread overview]
Message-ID: <DLUG3Q30BQDS.1WMLGJKNHOYPV@verdict.gg> (raw)
In-Reply-To: <ar--fEmqMyX8odNn@gpd4>

Hi Andrea,

On Fri, Oct 02, 2026, Andrea Righi wrote:
> Thanks for looking at this! I actually have a patch series in my backlog to
> introduce NUMA-balancing support in sched_ext. It makes NUMA hinting scans
> opt-in for BPF schedulers and exposes a task's preferred NUMA node to BPF.

That is great news, thanks. My patch was only a small sketch to show the
problem, so I am happy to leave it at that and follow your series
instead.

Opt-in scanning plus the preferred node exposed to BPF sounds like what
I was looking for. My scheduler runs on KVM hypervisors and reads
p->numa_preferred_nid to choose a home node for each vCPU thread,
falling back to the thread group's majority when a task has none. Under
SCX that value stops being updated, which is how I noticed.

> It also lets a BPF scheduler set a per-task memory target, which NUMA balancing
> can use when migrating pages after hinting faults.

This part sounds interesting too. Guests that span two nodes are the
hard case for me: today I can only follow the memory, I cannot ask for
it to follow the vCPUs.

> I can probably send the patch series at this point, it's not completely
> well-tested, but it might be useful to have it on the list, so that we can start
> discussing and improving it. I'll keep you in the loop.

Thanks, I will be watching for it. If it is of any use, I can try it on
a few hypervisors (2- and 4-node hosts) and share numbers for scan rate,
hint faults and time spent on the preferred node.

Thanks,
Vladimir

      reply	other threads:[~2026-10-02 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 12:45 Vladimir Vdovin
2026-10-02 14:23 ` Andrea Righi
2026-10-02 15:08   ` Vladimir Vdovin [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=DLUG3Q30BQDS.1WMLGJKNHOYPV@verdict.gg \
    --to=deliran@verdict.gg \
    --cc=arighi@nvidia.com \
    --cc=bsegall@google.com \
    --cc=changwoo@igalia.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=sh_def@163.com \
    --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

all inboxes | Powered by JetHome®