public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Segall <bsegall@google.com>
To: Peng Wang <rocking@linux.alibaba.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bristot@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Reorder throttle_cfs_rq() path
Date: Wed, 11 Nov 2020 12:27:07 -0800	[thread overview]
Message-ID: <xm26imab3ahw.fsf@google.com> (raw)
In-Reply-To: <f11dd2e3ab35cc538e2eb57bf0c99b6eaffce127.1604973978.git.rocking@linux.alibaba.com> (Peng Wang's message of "Tue, 10 Nov 2020 10:11:59 +0800")

Peng Wang <rocking@linux.alibaba.com> writes:

> As commit 39f23ce07b93 ("sched/fair: Fix unthrottle_cfs_rq() for
> leaf_cfs_rq list") does in unthrottle_cfs_rq(), throttle_cfs_rq()
> can also use the same pattern as dequeue_task_fair().
>
> There is no functional changes.

It's generally a bit more hassle and less clear, but the parallel to
dequeue_task_fair probably makes up for it.

Reviewed-by: Ben Segall <bsegall@google.com>

>
> Signed-off-by: Peng Wang <rocking@linux.alibaba.com>
> ---
>  kernel/sched/fair.c | 34 +++++++++++++++++++++++-----------
>  1 file changed, 23 insertions(+), 11 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 290f9e3..27a69af 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4779,25 +4779,37 @@ static bool throttle_cfs_rq(struct cfs_rq *cfs_rq)
>  		struct cfs_rq *qcfs_rq = cfs_rq_of(se);
>  		/* throttled entity or throttle-on-deactivate */
>  		if (!se->on_rq)
> -			break;
> +			goto done;
>  
> -		if (dequeue) {
> -			dequeue_entity(qcfs_rq, se, DEQUEUE_SLEEP);
> -		} else {
> -			update_load_avg(qcfs_rq, se, 0);
> -			se_update_runnable(se);
> -		}
> +		dequeue_entity(qcfs_rq, se, DEQUEUE_SLEEP);
>  
>  		qcfs_rq->h_nr_running -= task_delta;
>  		qcfs_rq->idle_h_nr_running -= idle_task_delta;
>  
> -		if (qcfs_rq->load.weight)
> -			dequeue = 0;
> +		if (qcfs_rq->load.weight) {
> +			/* Avoid re-evaluating load for this entity: */
> +			se = parent_entity(se);
> +			break;
> +		}
>  	}
>  
> -	if (!se)
> -		sub_nr_running(rq, task_delta);
> +	for_each_sched_entity(se) {
> +		struct cfs_rq *qcfs_rq = cfs_rq_of(se);
> +		/* throttled entity or throttle-on-deactivate */
> +		if (!se->on_rq)
> +			goto done;
> +
> +		update_load_avg(qcfs_rq, se, 0);
> +		se_update_runnable(se);
>  
> +		qcfs_rq->h_nr_running -= task_delta;
> +		qcfs_rq->idle_h_nr_running -= idle_task_delta;
> +	}
> +
> +	/* At this point se is NULL and we are at root level*/
> +	sub_nr_running(rq, task_delta);
> +
> +done:
>  	/*
>  	 * Note: distribution will already see us throttled via the
>  	 * throttled-list.  rq->lock protects completion.

      reply	other threads:[~2020-11-11 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10  2:11 [PATCH] sched/fair: Reorder throttle_cfs_rq() path Peng Wang
2020-11-11 20:27 ` Benjamin Segall [this message]

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=xm26imab3ahw.fsf@google.com \
    --to=bsegall@google.com \
    --cc=bristot@redhat.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rocking@linux.alibaba.com \
    --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