From: Peter Zijlstra <peterz@infradead.org>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org, containers@lists.linux-foundation.org
Subject: Re: [PATCH RFC 0/3] sched/fair: cpu time reserves for cgroups
Date: Mon, 16 May 2016 13:18:49 +0200 [thread overview]
Message-ID: <20160516111849.GN3193@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <146339085068.25295.7687045977863852568.stgit@buzz>
On Mon, May 16, 2016 at 12:36:19PM +0300, Konstantin Khlebnikov wrote:
> This feature allows to change cpu cgroup weight for a limited time.
>
> Cgroup interface:
> cpu.cfs_reserve_us - reserved time for each cpu.cfs_period_us
> cpu.cfs_reserve_shares - group weight during reserved time
>
> While cfs group consumes reserved cpu time it has different weight,
> thus it gets different vruntime penalty for that execution.
>
> ^ weight
> |
> |
> reserve |
> shares -------*
> | |
> | |
> | |
> shares - *-----------------*
> | |
> | |
> 0------|-----------------|-----------> time
> reserve quota
>
> Reserve can work as a "low limit": boost weight for "guaranteed" time,
> and as a "high limit": give normal weight for a limited time and allow
> utilize cpu when nobody else needs it.
>
You forgot to explain why I should care about this.
next prev parent reply other threads:[~2016-05-16 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 9:36 [PATCH RFC 0/3] sched/fair: cpu time reserves for cgroups Konstantin Khlebnikov
2016-05-16 9:36 ` [PATCH RFC 1/3] sched/fair: call __refill_cfs_bandwidth_runtime only for finite quota Konstantin Khlebnikov
2016-05-16 9:36 ` [PATCH RFC 2/3] sched/fair: copy taskgroup shares to each cfs_rq Konstantin Khlebnikov
2016-05-16 9:36 ` [PATCH RFC 3/3] sched/fair: pulse-weight modulation controller for cpu cgroup Konstantin Khlebnikov
2016-05-16 11:18 ` Peter Zijlstra [this message]
2016-05-16 12:22 ` [PATCH RFC 0/3] sched/fair: cpu time reserves for cgroups Konstantin Khlebnikov
2016-05-16 12:26 ` Peter Zijlstra
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=20160516111849.GN3193@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.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