From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: vincent.guittot@linaro.org
Cc: arighi@nvidia.com, bsegall@google.com, changwoo@igalia.com,
christian.loehle@arm.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, kprateek.nayak@amd.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
lukasz.luba@arm.com, mgorman@suse.de, mingo@redhat.com,
peterz@infradead.org, pierre.gondois@arm.com,
qyousef@layalina.io, rafael@kernel.org, rostedt@goodmis.org,
sched-ext@lists.linux.dev, sshegde@linux.ibm.com, tj@kernel.org,
void@manifault.com, vschneid@redhat.com
Subject: Re: [PATCH 18/18 v2] sched/fair: Take into account slice in EAS
Date: Wed, 7 Oct 2026 17:36:14 +0300 [thread overview]
Message-ID: <20261007143614.27368-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <20261002154415.2270586-19-vincent.guittot@linaro.org>
> When the cost is the same, take into account the slice of a task to try to
> select a CPU where is will run first.
'is'? It gives 'it' vibes more of 'is' vibes... (:>)
> static bool update_best_cpu(struct energy_cpu_stat *target,
> struct energy_cpu_stat *min,
> - int prev, struct sched_domain *sd)
> + int prev, struct sched_domain *sd,
> + struct task_struct *p)
> {
> + unsigned long task_slice = p->se.slice;
> +
> + /* Select the one where you can run first */
Again. A typo. An extra blank. I'll normally make a joke but,
I'm tired. ;-)
> + if (task_slice < get_rq_min_slice(cpu_rq(target->cpu)) &&
> + task_slice >= get_rq_min_slice(cpu_rq(min->cpu)))
> + return true;
> +
> + /* Favor previous CPU */
> if (target->cpu == prev)
> return true;
> if (min->cpu == prev)
> @@ -9762,7 +9771,7 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu)
> */
> if (target_perf < min_stat.min_perf)
> find_pd_cost(pd->em_pd, target_perf, &target_stat);
> - else if (!update_best_cpu(&target_stat, &min_stat, prev_cpu, sd))
> + else if (!update_best_cpu(&target_stat, &min_stat, prev_cpu, sd, p))
> continue;
>
> /* Save the new most efficient CPU of the PD */
Also,
Scene:
On the reworked version of feec(), we have this check:
if (p->on_rq && !p->se.sched_delayed && cpu == prev_cpu)
A little after and outside of this check, we call update_best_cpu().
Now, if this check can get true, on this state:
prev's min_slice cannot be bigger than p's task_slice.
So when target is prev the first check is always false,
and when min->cpu is prev, the second check is always true.
Also also, I have a really important issue abot the patch
series that can finish the whole patch series and end the world
itself...
The issue is...
I need to sleep.
Thanks,
Kayra
prev parent reply other threads:[~2026-10-07 14:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 15:43 [PATCH 00/18 v2] Improving latency of short slice tasks Vincent Guittot
2026-10-02 15:43 ` [PATCH 01/18 v2] sched/eevdf: Decay positive lag of sleeping entities Vincent Guittot
2026-10-02 15:43 ` [PATCH 02/18] sched/eevdf: Reset lag when waking up on idle cpu Vincent Guittot
2026-10-04 17:30 ` Kayra Cizmeci
2026-10-02 15:44 ` [PATCH 03/18 v2] sched/eevdf: Add per cpu cached min_slice Vincent Guittot
2026-10-02 15:44 ` [PATCH 04/18 v2] sched/eevdf: Compare min slice during wake_affine Vincent Guittot
2026-10-05 15:58 ` Kayra Cizmeci
2026-10-02 15:44 ` [PATCH 05/18 v2] sched/eevdf: Add min slice check when selecting CPU Vincent Guittot
2026-10-04 19:18 ` Kayra Cizmeci
2026-10-02 15:44 ` [PATCH 06/18 v2] sched/fair: Prepare select_task_rq_fair() to be called for new cases Vincent Guittot
2026-10-06 22:25 ` Tim Chen
2026-10-02 15:44 ` [PATCH 07/18] sched/fair: Add push task mechanism for fair Vincent Guittot
2026-10-07 2:45 ` Chen Yu
2026-10-02 15:44 ` [PATCH 08/18] sched/fair: Optimize " Vincent Guittot
2026-10-02 15:44 ` [PATCH 09/18 v2] sched/core: Add rq flag to tick parameters Vincent Guittot
2026-10-02 15:44 ` [PATCH 10/18 v2] sched/fair: Add force push task mechanism for fair Vincent Guittot
2026-10-06 19:24 ` Kayra Cizmeci
2026-10-02 15:44 ` [PATCH 11/18 v2] sched/fair: Support not wakeup case in select_idle_sibling Vincent Guittot
2026-10-07 17:55 ` Tim Chen
2026-10-02 15:44 ` [PATCH 12/18 v2] sched/eevdf: Try to push short slice task on a better CPU Vincent Guittot
2026-10-02 15:44 ` [PATCH 13/18 v2] sched/eevdf: Push short slice task that are not picked Vincent Guittot
2026-10-02 15:44 ` [PATCH 14/18 v2] sched/fair: Enable push task for preempt short Vincent Guittot
2026-10-02 15:44 ` [PATCH 15/18 v2] energy model: Add a get previous state function Vincent Guittot
2026-10-02 15:44 ` [PATCH 16/18 v2] sched/fair: Rework feec() to use cost instead of spare capacity Vincent Guittot
2026-10-02 15:44 ` [PATCH 17/18 v2] energy model: Remove unused em_cpu_energy() Vincent Guittot
2026-10-02 15:44 ` [PATCH 18/18 v2] sched/fair: Take into account slice in EAS Vincent Guittot
2026-10-07 14:36 ` Kayra Cizmeci [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=20261007143614.27368-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@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=lukasz.luba@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=sshegde@linux.ibm.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®