From: Benjamin Segall <bsegall@google.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: changhuaixin <changhuaixin@linux.alibaba.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
dtcccc@linux.alibaba.com, Juri Lelli <juri.lelli@redhat.com>,
khlebnikov@yandex-team.ru,
open list <linux-kernel@vger.kernel.org>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@redhat.com>,
Odin Ugedal <odin@uged.al>, Odin Ugedal <odin@ugedal.com>,
pauld@redhead.com, Paul Turner <pjt@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Shanpei Chen <shanpeic@linux.alibaba.com>,
Tejun Heo <tj@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH v5 1/3] sched/fair: Introduce the burstable CFS controller
Date: Tue, 25 May 2021 14:25:33 -0700 [thread overview]
Message-ID: <xm26pmxe4ib6.fsf@google.com> (raw)
In-Reply-To: <YKzVu2cOYRN9TZD3@hirez.programming.kicks-ass.net> (Peter Zijlstra's message of "Tue, 25 May 2021 12:47:23 +0200")
Peter Zijlstra <peterz@infradead.org> writes:
> On Mon, May 24, 2021 at 08:42:03PM +0800, changhuaixin wrote:
>
>> >> static inline struct cfs_bandwidth *tg_cfs_bandwidth(struct task_group *tg)
>> >> @@ -4651,6 +4666,9 @@ static int __assign_cfs_rq_runtime(struct cfs_bandwidth *cfs_b,
>> >> if (cfs_b->quota == RUNTIME_INF)
>> >> amount = min_amount;
>> >> else {
>> >> + if (!cfs_b->period_active)
>> >> + __refill_cfs_bandwidth_runtime(cfs_b);
>> >
>> > Why this call?
>>
>> As the cfs bandwidth timer stops on idle with runtime unfilled, refill runtime when it restarts to make
>> use of the underrun when period timer stops. Another way to do this might be:
>>
>> throttled = !list_empty(&cfs_b->throttled_cfs_rq);
>> cfs_b->nr_periods += overrun;
>>
>> + __refill_cfs_bandwidth_runtime(cfs_b);
>> +
>> /*
>> * idle depends on !throttled (for the case of a large deficit), and if
>> * we're going inactive then everything else can be deferred
>> */
>> if (cfs_b->idle && !throttled)
>> goto out_deactivate;
>>
>> - __refill_cfs_bandwidth_runtime(cfs_b);
>> -
>> if (!throttled) {
>>
>
> Ben, do you have a preference?
I think I prefer the latter, possibly with a
/* Refill extra burst quota even if cfs_b->idle */
next prev parent reply other threads:[~2021-05-25 21:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:34 [PATCH v5 0/3] sched/fair: Burstable CFS bandwidth controller Huaixin Chang
2021-05-20 12:34 ` [PATCH v5 1/3] sched/fair: Introduce the burstable CFS controller Huaixin Chang
2021-05-20 14:00 ` Odin Ugedal
2021-05-20 17:04 ` Tejun Heo
2021-05-21 9:09 ` changhuaixin
2021-05-21 9:38 ` Odin Ugedal
2021-05-21 12:38 ` changhuaixin
2021-05-21 14:00 ` Peter Zijlstra
2021-05-24 12:42 ` changhuaixin
2021-05-25 10:46 ` Peter Zijlstra
2021-05-31 6:59 ` luca abeni
2021-05-25 10:47 ` Peter Zijlstra
2021-05-25 21:25 ` Benjamin Segall [this message]
2021-05-25 10:49 ` Peter Zijlstra
2021-05-20 12:34 ` [PATCH v5 2/3] sched/fair: Add cfs bandwidth burst statistics Huaixin Chang
2021-05-20 14:11 ` Odin Ugedal
2021-05-21 12:42 ` changhuaixin
2021-05-21 14:05 ` Peter Zijlstra
2021-05-20 17:06 ` Tejun Heo
2021-05-21 14:01 ` Peter Zijlstra
2021-05-20 12:34 ` [PATCH v5 3/3] sched/fair: Add document for burstable CFS bandwidth Huaixin Chang
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=xm26pmxe4ib6.fsf@google.com \
--to=bsegall@google.com \
--cc=changhuaixin@linux.alibaba.com \
--cc=dietmar.eggemann@arm.com \
--cc=dtcccc@linux.alibaba.com \
--cc=juri.lelli@redhat.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=odin@uged.al \
--cc=odin@ugedal.com \
--cc=pauld@redhead.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=shanpeic@linux.alibaba.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.