mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>,
	peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org
Cc: 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: Fri, 21 Oct 2016 13:19:01 +0100	[thread overview]
Message-ID: <deef7d82-eae8-6f37-6c6d-fcb3523df97d@arm.com> (raw)
In-Reply-To: <1476695653-12309-5-git-send-email-vincent.guittot@linaro.org>

On 10/17/2016 10:14 AM, Vincent Guittot wrote:
> When a task moves from/to a cfs_rq, we set a flag which is then used to
> propagate the change at parent level (sched_entity and cfs_rq) during
> next update. If the cfs_rq is throttled, the flag will stay pending until
> the cfs_rw is unthrottled.

minor nit:

s/cfs_rw/cfs_rq

[...]

> @@ -8704,6 +8867,22 @@ static void detach_task_cfs_rq(struct task_struct *p)
>  	update_load_avg(se, 0);
>  	detach_entity_load_avg(cfs_rq, se);
>  	update_tg_load_avg(cfs_rq, false);
> +
> +#ifdef CONFIG_FAIR_GROUP_SCHED
> +	/*
> +	 * Propagate the detach across the tg tree to make it visible to the
> +	 * root
> +	 */
> +	se = se->parent;
> +	for_each_sched_entity(se) {
> +		cfs_rq = cfs_rq_of(se);
> +
> +		if (cfs_rq_throttled(cfs_rq))
> +			break;
> +
> +		update_load_avg(se, UPDATE_TG);
> +	}
> +#endif
>  }
>
>  static void attach_entity_cfs_rq(struct sched_entity *se)
> @@ -8722,6 +8901,22 @@ static void attach_entity_cfs_rq(struct sched_entity *se)
>  	update_load_avg(se, sched_feat(ATTACH_AGE_LOAD) ? 0 : SKIP_AGE_LOAD);
>  	attach_entity_load_avg(cfs_rq, se);
>  	update_tg_load_avg(cfs_rq, false);
> +
> +#ifdef CONFIG_FAIR_GROUP_SCHED
> +	/*
> +	 * Propagate the attach across the tg tree to make it visible to the
> +	 * root
> +	 */
> +	se = se->parent;
> +	for_each_sched_entity(se) {
> +		cfs_rq = cfs_rq_of(se);
> +
> +		if (cfs_rq_throttled(cfs_rq))
> +			break;
> +
> +		update_load_avg(se, UPDATE_TG);
> +	}
> +#endif
>  }

The 'detach across' and 'attach across' in detach_task_cfs_rq() and 
attach_entity_cfs_rq() do the same so couldn't you not create a function 
propagate_foo() for it? This would avoid this ifdef as well.

You could further create in your '[PATCH 1/6 v5] sched: factorize attach 
entity':

detach_entity_cfs_rq() {
   update_load_avg()
   detach_entity_load_avg()
   update_tg_load_avg()
   propagate_load_avg()
}

and then we would have:

attach_task_cfs_rq() -> attach_entity_cfs_rq() -> propagate_foo()
detach_task_cfs_rq() -> detach_entity_cfs_rq() -> propagate_foo()

I guess you didn't because it would be only called one time but this 
symmetric approaches are easier to remember (at least for me).

[...]

  reply	other threads:[~2016-10-21 12:19 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 [this message]
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
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=deef7d82-eae8-6f37-6c6d-fcb3523df97d@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=Morten.Rasmussen@arm.com \
    --cc=bsegall@google.com \
    --cc=kernellwp@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®