From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
dietmar.eggemann@arm.com, yuyang.du@intel.com,
Morten.Rasmussen@arm.com, linaro-kernel@lists.linaro.org,
pjt@google.com, bsegall@google.com, kernellwp@gmail.com
Subject: Re: [PATCH 4/6 v5] sched: propagate load during synchronous attach/detach
Date: Wed, 26 Oct 2016 13:45:22 +0200 [thread overview]
Message-ID: <20161026114522.GH3102@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1476695653-12309-5-git-send-email-vincent.guittot@linaro.org>
On Mon, Oct 17, 2016 at 11:14:11AM +0200, Vincent Guittot wrote:
> +/* Take into account change of load of a child task group */
> +static inline void
> +update_tg_cfs_load(struct cfs_rq *cfs_rq, struct sched_entity *se)
> +{
> + struct cfs_rq *gcfs_rq = group_cfs_rq(se);
> + long delta, load = gcfs_rq->avg.load_avg;
> +
> + /*
> + * If the load of group cfs_rq is null, the load of the
> + * sched_entity will also be null so we can skip the formula
> + */
Does it make sense to do:
if (!load)
goto no_load;
and avoid the indent?
> + if (load) {
> + long tg_load;
> +
> + /* Get tg's load and ensure tg_load > 0 */
> + tg_load = atomic_long_read(&gcfs_rq->tg->load_avg) + 1;
> +
> + /* Ensure tg_load >= load and updated with current load*/
> + tg_load -= gcfs_rq->tg_load_avg_contrib;
> + tg_load += load;
> +
> + /*
> + * We need to compute a correction term in the case that the
> + * task group is consuming more cpu than a task of equal
> + * weight. A task with a weight equals to tg->shares will have
> + * a load less or equal to scale_load_down(tg->shares).
+ *
> + * Similarly, the sched_entities that represent the task group
> + * at parent level, can't have a load higher than
> + * scale_load_down(tg->shares). And the Sum of sched_entities'
> + * load must be <= scale_load_down(tg->shares).
> + */
> + if (tg_load > scale_load_down(gcfs_rq->tg->shares)) {
> + /* scale gcfs_rq's load into tg's shares*/
> + load *= scale_load_down(gcfs_rq->tg->shares);
> + load /= tg_load;
> + }
> + }
> +
no_load:
> + delta = load - se->avg.load_avg;
> +
> + /* Nothing to update */
> + if (!delta)
> + return;
> +
> + /* Set new sched_entity's load */
> + se->avg.load_avg = load;
> + se->avg.load_sum = se->avg.load_avg * LOAD_AVG_MAX;
> +
> + /* Update parent cfs_rq load */
> + add_positive(&cfs_rq->avg.load_avg, delta);
> + cfs_rq->avg.load_sum = cfs_rq->avg.load_avg * LOAD_AVG_MAX;
> +
> + /*
> + * If the sched_entity is already enqueued, we also have to update the
> + * runnable load avg.
> + */
> + if (se->on_rq) {
> + /* Update parent cfs_rq runnable_load_avg */
> + add_positive(&cfs_rq->runnable_load_avg, delta);
> + cfs_rq->runnable_load_sum = cfs_rq->runnable_load_avg * LOAD_AVG_MAX;
> + }
> +}
next prev parent reply other threads:[~2016-10-26 11:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 9:14 [PATCH 0/6 v5] sched: reflect sched_entity move into task_group's load Vincent Guittot
2016-10-17 9:14 ` [PATCH 1/6 v5] sched: factorize attach entity Vincent Guittot
2016-10-17 9:14 ` [PATCH 2/6 v5] sched: fix hierarchical order in rq->leaf_cfs_rq_list Vincent Guittot
2016-10-17 9:14 ` [PATCH 3/6 v5] sched: factorize PELT update Vincent Guittot
2016-10-26 11:41 ` Peter Zijlstra
2016-10-26 12:56 ` Vincent Guittot
2016-10-17 9:14 ` [PATCH 4/6 v5] sched: propagate load during synchronous attach/detach Vincent Guittot
2016-10-21 12:19 ` Dietmar Eggemann
2016-10-26 7:05 ` Vincent Guittot
2016-10-26 11:16 ` Peter Zijlstra
2016-10-26 12:31 ` Vincent Guittot
2016-10-26 10:54 ` Peter Zijlstra
2016-10-26 12:31 ` Vincent Guittot
2016-10-26 14:28 ` Peter Zijlstra
2016-10-26 18:40 ` Vincent Guittot
2016-10-26 11:45 ` Peter Zijlstra [this message]
2016-10-17 9:14 ` [PATCH 5/6 v5] sched: propagate asynchrous detach Vincent Guittot
2016-10-17 9:14 ` [PATCH 6/6 v5] sched: fix task group initialization Vincent Guittot
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=20161026114522.GH3102@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Morten.Rasmussen@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=kernellwp@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjt@google.com \
--cc=vincent.guittot@linaro.org \
--cc=yuyang.du@intel.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