From: Christian Loehle <christian.loehle@arm.com>
To: Peter Zijlstra <peterz@infradead.org>, tj@kernel.org
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
longman@redhat.com, hannes@cmpxchg.org, mkoutny@suse.com,
void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
cgroups@vger.kernel.org, sched-ext@lists.linux.dev,
liuwenfang@honor.com, tglx@linutronix.de
Subject: Re: [RFC][PATCH 0/3] sched/ext: Cleanup pick_task_scx()
Date: Tue, 7 Oct 2025 13:40:22 +0100 [thread overview]
Message-ID: <7d13109d-28e6-46fa-898c-388fc9912710@arm.com> (raw)
In-Reply-To: <20251006104652.630431579@infradead.org>
On 10/6/25 11:46, Peter Zijlstra wrote:
> Hi,
>
> So I had a poke at 'give @rf to pick_task() and fold balance_scx() into
> pick_task_scx()' option to see how terrible it was. Turns out, not terrible at
> all.
>
> I've ran the sched_ext selftest and stress-ng --race-sched 0 thing with various
> scx_* thingies on.
>
> These patches were done on top of the 'sched_change' patches posted just now:
>
> https://lkml.kernel.org/r/20251006104402.946760805@infradead.org
>
> The combined set is also available here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git sched/cleanup-pick
>
FWIW I didn't run into any issues either running some scx scheduler + workload
combinations.
next prev parent reply other threads:[~2025-10-07 12:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 10:46 Peter Zijlstra
2025-10-06 10:46 ` [RFC][PATCH 1/3] sched: Detect per-class runqueue changes Peter Zijlstra
2025-10-07 10:08 ` Juri Lelli
2025-10-07 10:16 ` Peter Zijlstra
2025-10-07 10:26 ` Juri Lelli
2025-10-16 9:33 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2025-10-06 10:46 ` [RFC][PATCH 2/3] sched: Add support to pick functions to take rf Peter Zijlstra
2025-10-08 13:16 ` Vincent Guittot
2025-10-08 13:58 ` Peter Zijlstra
2025-10-08 15:22 ` Vincent Guittot
2025-10-08 20:34 ` Tejun Heo
2025-10-09 7:17 ` Vincent Guittot
2025-10-13 11:04 ` Peter Zijlstra
2025-10-13 11:09 ` Peter Zijlstra
2025-10-13 13:06 ` Vincent Guittot
2025-10-13 17:20 ` Tejun Heo
2025-10-16 9:33 ` [tip: sched/core] " tip-bot2 for Joel Fernandes
2025-10-06 10:46 ` [RFC][PATCH 3/3] sched/ext: Fold balance_scx() into pick_task_scx() Peter Zijlstra
2025-10-16 9:33 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2025-10-07 12:40 ` Christian Loehle [this message]
2025-10-07 21:48 ` [RFC][PATCH 0/3] sched/ext: Cleanup pick_task_scx() Tejun Heo
2025-10-08 9:11 ` Peter Zijlstra
2025-10-08 20:21 ` 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=7d13109d-28e6-46fa-898c-388fc9912710@arm.com \
--to=christian.loehle@arm.com \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwenfang@honor.com \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=tglx@linutronix.de \
--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®