From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Jiang Biao <benbjiang@gmail.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, Jiang Biao <benbjiang@tencent.com>
Subject: Re: [PATCH RFC v2] sched/fair: simplify the work when reweighting entity
Date: Tue, 11 Aug 2020 11:50:12 +0200 [thread overview]
Message-ID: <9149cf7c-df81-cf9d-65f7-a51d4ec76f78@arm.com> (raw)
In-Reply-To: <20200806161406.22629-1-benbjiang@tencent.com>
On 06/08/2020 18:14, Jiang Biao wrote:
> From: Jiang Biao <benbjiang@tencent.com>
>
> If a se is on_rq when reweighting entity, all we need should be
> updating the load of cfs_rq, other dequeue/enqueue work could be
> redundant, such as,
> * nr_running--/nr_running++
>
> Even though the following dequeue/enqueue path would never be reached
> * account_numa_dequeue/account_numa_enqueue
> * list_del/list_add from/into cfs_tasks
> but it could be a little confusing.
>
> Simplifying the logic could be helpful to reduce a litte overhead for
> hot path, and make it cleaner and more readable.
LGTM. I guess you have to resend it w/o the RFC tag.
Maybe you can rework the patch header a little?
Something like this:
The code in reweight_entity() can be simplified.
For a sched entity on the rq, the entity accounting can be replaced by
cfs_rq instantaneous load updates currently called from within the
entity accounting.
Even though an entity on the rq can't represent a task in
reweight_entity() (a task is always dequeued before calling this
function) and so the numa task accounting and the rq->cfs_tasks list
management of the entity accounting are never called, the redundant
cfs_rq->nr_running decrement/increment will be avoided.
>
> Signed-off-by: Jiang Biao <benbjiang@tencent.com>
> ---
> v2<-v1:
> - Amend the commit log.
>
> kernel/sched/fair.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 04fa8dbcfa4d..18a8fc7bd0de 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -3086,7 +3086,7 @@ static void reweight_entity(struct cfs_rq *cfs_rq, struct sched_entity *se,
> /* commit outstanding execution time */
> if (cfs_rq->curr == se)
> update_curr(cfs_rq);
> - account_entity_dequeue(cfs_rq, se);
> + update_load_sub(&cfs_rq->load, se->load.weight);
> }
> dequeue_load_avg(cfs_rq, se);
>
> @@ -3102,7 +3102,7 @@ static void reweight_entity(struct cfs_rq *cfs_rq, struct sched_entity *se,
>
> enqueue_load_avg(cfs_rq, se);
> if (se->on_rq)
> - account_entity_enqueue(cfs_rq, se);
> + update_load_add(&cfs_rq->load, se->load.weight);
>
> }
next prev parent reply other threads:[~2020-08-11 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 16:14 Jiang Biao
2020-08-11 9:50 ` Dietmar Eggemann [this message]
2020-08-11 11:19 ` [PATCH RFC v2] sched/fair: simplify the work when reweighting entity(Internet mail) benbjiang(蒋彪)
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=9149cf7c-df81-cf9d-65f7-a51d4ec76f78@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=benbjiang@gmail.com \
--cc=benbjiang@tencent.com \
--cc=bsegall@google.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 \
/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®