[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC=E7cUgALi4g19GsDZQemHafQfaSpjY1XUo3Swrv_g1PaWejQ@mail.gmail.com>
Date: Mon, 17 Feb 2020 13:56:29 -0600
From: Dave Chiluk <chiluk+linux@...eed.com>
To: Ben Segall <bsegall@...gle.com>
Cc: Konstantin Khlebnikov <khlebnikov@...dex-team.ru>,
Peter Zijlstra <peterz@...radead.org>, cgroups@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>, Mel Gorman <mgorman@...e.de>,
Cong Wang <xiyou.wangcong@...il.com>,
Dietmar Eggemann <dietmar.eggemann@....com>
Subject: Re: [PATCH v2] sched/fair: add burst to cgroup cpu bandwidth controller
On Fri, Feb 14, 2020 at 12:55 PM <bsegall@...gle.com> wrote:
> I'm not sure that starting with full burst runtime is best, though it
> definitely seems likely to be one of those things where sometimes it's
> what you want and sometimes it's not.
We (Indeed) definitely want to start with a full burst bank in most
cases, as this would help with slow/throttled start-up times for our
Jitted and interpreter-based language applications. I agree that it
would be nice to have it be configurable.
Dave.
fyi. Unfortunately, this e-mail may be temporarily turned off for the
next few weeks, I apologize in advance for any bounced messages to me.
Powered by blists - more mailing lists