From: Peter Zijlstra <peterz@infradead.org>
To: Yiwei Lin <s921975628@gmail.com>
Cc: mingo@redhat.com, wuyun.abel@bytedance.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, s921975627@gmail.com
Subject: Re: [PATCH] sched/fair: Update min_vruntime for reweight_entity() correctly
Date: Mon, 20 Nov 2023 12:48:35 +0100 [thread overview]
Message-ID: <20231120114835.GS8262@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20231117080106.12890-1-s921975628@gmail.com>
On Fri, Nov 17, 2023 at 04:01:06PM +0800, Yiwei Lin wrote:
> Since reweight_entity() may have chance to change the weight of
> cfs_rq->curr entity, we should also update_min_vruntime() if
> this is the case
>
> Fixes: eab03c23c2a1 ("sched/eevdf: Fix vruntime adjustment on reweight")
> Signed-off-by: Yiwei Lin <s921975628@gmail.com>
Right, but as you wrote in your other patch, min_vruntime isn't all that
critical anymore. I'll go queue this in sched/core, I don't think this
warrants /urgent.
> ---
> kernel/sched/fair.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 07f555857..6fb89f4a3 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -3815,17 +3815,17 @@ static void reweight_entity(struct cfs_rq *cfs_rq, struct sched_entity *se,
> enqueue_load_avg(cfs_rq, se);
> if (se->on_rq) {
> update_load_add(&cfs_rq->load, se->load.weight);
> - if (!curr) {
> - /*
> - * The entity's vruntime has been adjusted, so let's check
> - * whether the rq-wide min_vruntime needs updated too. Since
> - * the calculations above require stable min_vruntime rather
> - * than up-to-date one, we do the update at the end of the
> - * reweight process.
> - */
> + if (!curr)
> __enqueue_entity(cfs_rq, se);
> - update_min_vruntime(cfs_rq);
> - }
> +
> + /*
> + * The entity's vruntime has been adjusted, so let's check
> + * whether the rq-wide min_vruntime needs updated too. Since
> + * the calculations above require stable min_vruntime rather
> + * than up-to-date one, we do the update at the end of the
> + * reweight process.
> + */
> + update_min_vruntime(cfs_rq);
> }
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-11-20 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 8:01 [PATCH] sched/fair: Update min_vruntime for reweight_entity() correctly Yiwei Lin
2023-11-17 8:05 ` Abel Wu
2023-11-20 11:48 ` Peter Zijlstra [this message]
2023-11-29 14:55 ` [tip: sched/core] " tip-bot2 for Yiwei Lin
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 11:42 [PATCH] " Yiwei Lin
2023-11-16 11:52 ` Abel Wu
2023-11-17 7:34 ` Abel Wu
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=20231120114835.GS8262@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=s921975627@gmail.com \
--cc=s921975628@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=wuyun.abel@bytedance.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