From: Peter Zijlstra <peterz@infradead.org>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
"wangtao (EQ)" <wangtao554@huawei.com>,
mingo@redhat.com, juri.lelli@redhat.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
tanghui20@huawei.com, zhangqiao22@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/eevdf: Update se->vprot in reweight_entity()
Date: Fri, 23 Jan 2026 22:31:40 +0100 [thread overview]
Message-ID: <20260123213140.GB3268448@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <44c45e82-25e7-4d70-a46d-fb34e6aacbd6@amd.com>
On Fri, Jan 23, 2026 at 10:09:05PM +0530, K Prateek Nayak wrote:
> > @@ -3823,6 +3830,8 @@ static void reweight_entity(struct cfs_rq *cfs_rq, struct sched_entity *se,
> > enqueue_load_avg(cfs_rq, se);
> > if (se->on_rq) {
> > place_entity(cfs_rq, se, 0);
> > + if (vprot)
> > + se->vprot = se->vruntime + vprot;
>
> Scaling vprot makes sense too. Can there be a problem where "vprot"
> turns to zero on scaling (weight > (vprot * se->load.weight)) but we
> don't end up updating "se->vprot"?
Yeah, this can happen, but in that case the thing is 'small'. I'll see
if I can fix it though.
> Since we are looking at these bits, can you also please take a look at
> https://lore.kernel.org/lkml/20251226001731.3730586-1-quzicheng@huawei.com/
> which I feel might be a genuine issue when we are reweight the curr's
> vruntime.
Oh, I hadn't found that yet -- people should know better than to send
mail during x-mas ;-)
next prev parent reply other threads:[~2026-01-23 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:31 Wang Tao
2026-01-21 4:21 ` K Prateek Nayak
2026-01-21 9:33 ` wangtao (EQ)
2026-01-21 17:00 ` Vincent Guittot
2026-01-22 4:38 ` K Prateek Nayak
2026-01-23 16:38 ` Vincent Guittot
2026-01-22 7:52 ` wangtao (EQ)
2026-01-23 17:32 ` Vincent Guittot
2026-01-23 15:38 ` Peter Zijlstra
2026-01-23 16:39 ` K Prateek Nayak
2026-01-23 21:31 ` Peter Zijlstra [this message]
2026-01-23 17:37 ` Vincent Guittot
2026-02-23 10:25 ` [tip: sched/urgent] " tip-bot2 for Wang Tao
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=20260123213140.GB3268448@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=tanghui20@huawei.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangtao554@huawei.com \
--cc=zhangqiao22@huawei.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®