From: Gaowei Pu <pugaowei@oppo.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH_V2] sched/fair: updates weight of cfs_rq before update_cfs_group() in enqueue_entity()
Date: Tue, 11 Jun 2024 11:36:31 +0800 [thread overview]
Message-ID: <f35822e5-48f3-4b47-bef9-ad17f5e61359@oppo.com> (raw)
In-Reply-To: <20240603091805.858-1-pugaowei@oppo.com>
ping...
On 2024/6/3 17:18, Gaowei.Pu wrote:
> From: pugaowei <pugaowei@oppo.com>
>
> we should update the weight of cfs_rq before update_cfs_group().
> Ensure that we can get accurate shares of the cfs_rq when its
> weights changes. we can find this work was done correctly in
> dequeue_entity(). so fix it.
>
> patch_V1 :
> https://lore.kernel.org/lkml/20240531030833.3375-1-pugaowei@oppo.com/T/#u
> trigger a warnning below because of the changing order of
> account_entity_enqueue().
>
> [ 0.400603][ T0] ? __warn (kernel/panic.c:693)
>
> [ 0.400603][ T0] ? place_entity (kernel/sched/fair.c:5256 (discriminator 1))
>
> [ 0.400603][ T0] ? report_bug (lib/bug.c:180 lib/bug.c:219)
>
> [ 0.400603][ T0] ? handle_bug (arch/x86/kernel/traps.c:239)
>
> [ 0.400603][ T0] ? exc_invalid_op (arch/x86/kernel/traps.c:260 (discriminator 1))
>
> [ 0.400603][ T0] ? asm_exc_invalid_op (arch/x86/include/asm/idtentry.h:621)
>
> [ 0.400603][ T0] ? place_entity (kernel/sched/fair.c:5256 (discriminator 1))
>
> [ 0.400603][ T0] ? place_entity (kernel/sched/fair.c:5182)
>
> [ 0.400603][ T0] enqueue_entity (kernel/sched/fair.c:5328)
>
> [ 0.400603][ T0] enqueue_task_fair (kernel/sched/fair.c:6785)
>
> V2 fix the warnning and keep the lag without inflating it when it is
> the first sched_entity queued on the cfs_rq.
>
> Signed-off-by: pugaowei <pugaowei@oppo.com>
> ---
> kernel/sched/fair.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 8a5b1ae0aa55..2fb1fbcfdda3 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5190,12 +5190,12 @@ place_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> *
> * EEVDF: placement strategy #1 / #2
> */
> - if (sched_feat(PLACE_LAG) && cfs_rq->nr_running) {
> + if (sched_feat(PLACE_LAG)) {
> struct sched_entity *curr = cfs_rq->curr;
> - unsigned long load;
> + unsigned long load, se_load;
>
> lag = se->vlag;
> -
> + se_load = scale_load_down(se->load.weight);
> /*
> * If we want to place a task and preserve lag, we have to
> * consider the effect of the new entity on the weighted
> @@ -5252,9 +5252,13 @@ place_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> if (curr && curr->on_rq)
> load += scale_load_down(curr->load.weight);
>
> - lag *= load + scale_load_down(se->load.weight);
> - if (WARN_ON_ONCE(!load))
> - load = 1;
> + lag *= load + se_load;
> + /*
> + * we just need to keep the lag whithout inflating it when the se is
> + * the first sched_entity queued on cfs_rq.
> + */
> + if (!load)
> + load = se_load;
> lag = div_s64(lag, load);
> }
>
> @@ -5304,6 +5308,12 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> */
> update_load_avg(cfs_rq, se, UPDATE_TG | DO_ATTACH);
> se_update_runnable(se);
> +
> + /*
> + * we should update the weight of cfs_rq before update_cfs_group.
> + * Ensure we can get accurate shares of the cfs_rq when its weights changes.
> + */
> + account_entity_enqueue(cfs_rq, se);
> /*
> * XXX update_load_avg() above will have attached us to the pelt sum;
> * but update_cfs_group() here will re-adjust the weight and have to
> @@ -5318,8 +5328,6 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
> if (!curr)
> place_entity(cfs_rq, se, flags);
>
> - account_entity_enqueue(cfs_rq, se);
> -
> /* Entity has migrated, no longer consider this task hot */
> if (flags & ENQUEUE_MIGRATED)
> se->exec_start = 0;
next prev parent reply other threads:[~2024-06-11 3:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 9:18 Gaowei.Pu
2024-06-11 3:36 ` Gaowei Pu [this message]
2024-06-11 10:59 ` Vincent Guittot
2024-06-11 11:55 ` Gaowei Pu
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=f35822e5-48f3-4b47-bef9-ad17f5e61359@oppo.com \
--to=pugaowei@oppo.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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®