From: Abel Wu <wuyun.abel@bytedance.com>
To: Yiwei Lin <s921975628@gmail.com>, mingo@redhat.com, peterz@infradead.org
Cc: vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Update min_vruntime for reweight_entity() correctly
Date: Fri, 17 Nov 2023 15:34:05 +0800 [thread overview]
Message-ID: <96194f8a-4e3f-4563-83d0-c754e1d2abd3@bytedance.com> (raw)
In-Reply-To: <30fa2ed2-dfee-4dbf-bb44-1b0374877706@bytedance.com>
On 11/16/23 7:52 PM, Abel Wu Wrote:
> Please add a Fix tag like this:
>
> Fixes: eab03c23c2a1 ("sched/eevdf: Fix vruntime adjustment on reweight")
Can you resend this patch with this fix tag please?
>
> On 11/16/23 7:42 PM, 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
>>
>> Signed-off-by: Yiwei Lin <s921975628@gmail.com>
>> ---
>> 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);
>> }
>> }
>
> LGTM, thanks!
next prev parent reply other threads:[~2023-11-17 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:42 Yiwei Lin
2023-11-16 11:52 ` Abel Wu
2023-11-17 7:34 ` Abel Wu [this message]
2023-11-17 8:01 Yiwei Lin
2023-11-17 8:05 ` Abel Wu
2023-11-20 11:48 ` Peter Zijlstra
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=96194f8a-4e3f-4563-83d0-c754e1d2abd3@bytedance.com \
--to=wuyun.abel@bytedance.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=s921975628@gmail.com \
--cc=vincent.guittot@linaro.org \
/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®