mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
	kprateek.nayak@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Fix flat hierarchy
Date: Fri, 14 Aug 2026 16:16:53 +0200	[thread overview]
Message-ID: <20260814141653.GB687043@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAKfTPtBifu-TBbQ-jLxTqjmCD+wbpdtATTrCuDTP8suc3GvEJA@mail.gmail.com>

On Fri, Aug 14, 2026 at 02:51:20PM +0200, Vincent Guittot wrote:
> On Fri, 14 Aug 2026 at 13:22, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > On Fri, Aug 14, 2026 at 11:26:13AM +0200, Vincent Guittot wrote:
> >
> > > For the enqueue, the 1st requeue_delayed_entity() which is the main
> > > path for delayed task, requires the update. Then another one before
> > > reweight_eevdf(cfs_rq, se, weight, false); in the !curr case.
> > >
> > > But I'm not sure we want to spread this in different places.
> >
> > Fair enough. I'll test the below and then push to sched/urgent.
> 
> I tested this patch on sched/core.
> 
> That being said, 7.2 wants something like below for requeued_delayed_entity()
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index fd3edf72fb6e..3defda0e2f83 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -7802,6 +7802,8 @@ requeue_delayed_entity(struct sched_entity *se)
>         WARN_ON_ONCE(!se->sched_delayed);
>         WARN_ON_ONCE(!se->on_rq);
> 
> +       update_curr(cfs_rq);
> +
>         if (update_entity_lag(cfs_rq, se)) {
>                 cfs_rq->nr_queued--;
>                 if (se != cfs_rq->curr)
> 
> So I would put the cahnge above in sched/urgent and the patch
> discussed here in sched/core

Right. I've pushed out sched/urgent and sched/core to queue.git. If you
could double check that, I'll push them out to tip later today.

For now, I'm going to go melt someplace outside for a bit.

  reply	other threads:[~2026-08-14 14:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 12:50 Vincent Guittot
2026-08-12 14:03 ` Peter Zijlstra
2026-08-12 14:21   ` Vincent Guittot
2026-08-13 10:31     ` Peter Zijlstra
2026-08-13 10:49       ` Vincent Guittot
2026-08-14  9:26         ` Vincent Guittot
2026-08-14 11:22           ` Peter Zijlstra
2026-08-14 12:51             ` Vincent Guittot
2026-08-14 14:16               ` Peter Zijlstra [this message]
2026-08-14 14:31                 ` Vincent Guittot
2026-08-14 19:35 ` [tip: sched/core] " tip-bot2 for Vincent Guittot

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=20260814141653.GB687043@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bsegall@google.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=rostedt@goodmis.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®