mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, linux-kernel@vger.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,
	kprateek.nayak@amd.com,  joshdon@google.com, tj@kernel.org,
	jakub@okonski.org
Subject: Re: [PATCH 2/3] sched/fair: Make cfs_rq::idle the sum of ancestor tg::idle
Date: Fri, 6 Nov 2026 11:57:03 +0300	[thread overview]
Message-ID: <au2VkE9005PlW8VN@scheduler.schedules> (raw)
In-Reply-To: <20261106083106.GC1779021@noisy.programming.kicks-ass.net>

On Fri, Nov 06, 2026 at 09:31:06AM +0100, Peter Zijlstra wrote:
> On Thu, Nov 05, 2026 at 10:20:00PM +0300, Kayra Cizmeci wrote:
> > On Thu, Nov 05, 2026 at 05:55:27PM +0100, Peter Zijlstra wrote:
> > > Rather than keeping cfs_rq::idle as a copy of tg::idle, make it the sum of
> > > all ancestor tg::idle. This makes it trivial to tell if the current cgroup
> > > is marked idle somewhere along its ancestral path.
> > > 
> > > This makes se_id_idle() behave differently. Notably is will now be true
> > > when there is a idle cgroup anywhere in the ancestor path. This
> > > addresses an issue where preemption of cgroup::idle was overlooked when
> > > flattening the runqueue.
> > 
> > How? The diff doesn't touches se_is_idle(). se_is_idle() just looks to
> > the policy for tasks:
> > 
> > static int se_is_idle(struct sched_entity *se)
> > {
> > 	if (entity_is_task(se))
> > 		return task_has_idle_policy(task_of(se));
> > 	return cfs_rq_is_idle(group_cfs_rq(se));
> > }
> 
> > Or am I getting something wrong?
> 
> cfs_rq_is_idle() := cfs_rq->idle > 0
> 
> and cfs_rq->idle is now getting incremented for the whole subtree. So if
> any ancestor is idle, this is now true.


Yeah, it is for group path. But we call se_is_idle for tasks in
wakeup_preempt_fair(). Not groups, no?

  parent reply	other threads:[~2026-11-06  8:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 16:55 [PATCH 0/3] sched/fair: Fix cgroup::idle preemption Peter Zijlstra
2026-11-05 16:55 ` [PATCH 1/3] sched/fair: Use guard in sched_group_set_idle() Peter Zijlstra
2026-11-05 17:42   ` Kayra Cizmeci
2026-11-06 16:04   ` Vincent Guittot
2026-11-05 16:55 ` [PATCH 2/3] sched/fair: Make cfs_rq::idle the sum of ancestor tg::idle Peter Zijlstra
2026-11-05 19:20   ` Kayra Cizmeci
2026-11-06  8:31     ` Peter Zijlstra
2026-11-06  8:53       ` Peter Zijlstra
2026-11-06  9:01         ` Kayra Cizmeci
2026-11-06  8:57       ` Kayra Cizmeci [this message]
2026-11-06  9:01         ` Peter Zijlstra
2026-11-06  9:11           ` Kayra Cizmeci
2026-11-06 16:24           ` Vincent Guittot
2026-11-05 16:55 ` [RFC][PATCH 3/3] sched/eevdf: Fix sched idle task group preemption Peter Zijlstra
2026-11-05 20:10   ` Kayra Cizmeci

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=au2VkE9005PlW8VN@scheduler.schedules \
    --to=kayracizmeci@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jakub@okonski.org \
    --cc=joshdon@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®