From: Tejun Heo <tj@kernel.org>
To: Odin Ugedal <odin@uged.al>
Cc: Huaixin Chang <changhuaixin@linux.alibaba.com>,
Benjamin Segall <bsegall@google.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>,
pauld@redhead.com, Peter Zijlstra <peterz@infradead.org>,
Paul Turner <pjt@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
shanpeic@linux.alibaba.com,
Vincent Guittot <vincent.guittot@linaro.org>,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH v5 1/3] sched/fair: Introduce the burstable CFS controller
Date: Thu, 20 May 2021 13:04:23 -0400 [thread overview]
Message-ID: <YKaWl7A6N5Jyyi01@slm.duckdns.org> (raw)
In-Reply-To: <CAFpoUr2mNO87XFAyHF=HA3f6KC8EkuGrwQQe54q4kmF1WgfG7w@mail.gmail.com>
Hello, Odin.
On Thu, May 20, 2021 at 04:00:29PM +0200, Odin Ugedal wrote:
> > cpu.max
> > A read-write two value file which exists on non-root cgroups.
> > The default is "max 100000".
>
> This will become a "three value file", and I know a few user space projects
> who parse this file by splitting on the middle space. I am not sure if they are
> "wrong", but I don't think we usually break such things. Not sure what
> Tejun thinks about this.
Good point. I haven't thought about that. It would make more sense to
separate it out to a separate file then - e.g. sth like cpu.max.burst, but
it seems like there are important questions to answer before adding new
interfaces.
Thanks.
--
tejun
next prev parent reply other threads:[~2021-05-20 17:04 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 [this message]
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
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=YKaWl7A6N5Jyyi01@slm.duckdns.org \
--to=tj@kernel.org \
--cc=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=pauld@redhead.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=shanpeic@linux.alibaba.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).