From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: christian.loehle@arm.com
Cc: beata.michalska@arm.com, cl@gentwo.org,
daniel.lezcano@kernel.org, dietmar.eggemann@arm.com,
elif.topuz@arm.com, juri.lelli@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, mingo@redhat.com, peterz@infradead.org,
rafael@kernel.org, rostedt@goodmis.org, sh@gentwo.org,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH 2/2] sched/fair: Randomize equally shallow slow-path candidates
Date: Thu, 17 Sep 2026 17:16:57 +0300 [thread overview]
Message-ID: <20260917141658.14490-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <b129997a-8d49-41be-a93a-7e0343c952e3@arm.com>
> Actually about the last part, I'm leaning towards sticking with v1, because
> that is actually the current upstream behaviour. !idle CPUs currently trump
> any CPU seen so far, but preserve min_exit_latency, therefore sticking it
> into the shallowest seen reservoir is consistent IMO (although we can
> certainly debate if that should be the case).
> I'd prefer sending a follow-up with an idle helper and making a properly
> defined policy there, but that's adjacent to this patch.
Hello Christian,
I could send a patch about this if you want, after making sure about
everything, obviously.
I'm a bit sick, so if you say yes, I could be slow. But I don't think
it will take more than 3 days after your answer.
Thanks,
Kayra :>
next prev parent reply other threads:[~2026-09-17 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 10:01 [PATCH 0/2] sched/fair: Randomize equally shallow idle CPU picks Christian Loehle
2026-09-16 10:01 ` [PATCH 1/2] sched/fair: Drop idle recency from slow-path CPU selection Christian Loehle
2026-09-17 13:28 ` Vincent Guittot
2026-09-16 10:01 ` [PATCH 2/2] sched/fair: Randomize equally shallow slow-path candidates Christian Loehle
2026-09-16 11:06 ` Kayra Cizmeci
2026-09-16 11:10 ` Christian Loehle
2026-09-16 11:12 ` Christian Loehle
2026-09-16 11:46 ` Kayra Cizmeci
2026-09-16 19:43 ` Shubhang
2026-09-17 7:47 ` Christian Loehle
2026-09-17 9:58 ` Christian Loehle
2026-09-17 14:02 ` Vincent Guittot
2026-09-17 14:16 ` Kayra Cizmeci [this message]
2026-09-17 14:08 ` Vincent Guittot
2026-09-17 14:22 ` Christian Loehle
2026-09-17 15:08 ` Vincent Guittot
2026-09-17 15:17 ` Christian Loehle
2026-09-24 12:44 ` [PATCH 0/2] sched/fair: Randomize equally shallow idle CPU picks Muhammad Usama Anjum
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=20260917141658.14490-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=beata.michalska@arm.com \
--cc=christian.loehle@arm.com \
--cc=cl@gentwo.org \
--cc=daniel.lezcano@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=elif.topuz@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sh@gentwo.org \
--cc=vincent.guittot@linaro.org \
--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