From: Paul Menage <menage@google.com>
To: bharata@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Gautham R Shenoy <ego@in.ibm.com>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Pavel Emelyanov <xemul@openvz.org>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org,
Linux Containers <containers@lists.linux-foundation.org>,
Herbert Poetzl <herbert@13thfloor.at>
Subject: Re: [RFC] CPU hard limits
Date: Fri, 5 Jun 2009 01:53:15 -0700 [thread overview]
Message-ID: <6599ad830906050153i1afd104fqe70f681317349142@mail.gmail.com> (raw)
In-Reply-To: <20090604053649.GA3701@in.ibm.com>
On Wed, Jun 3, 2009 at 10:36 PM, Bharata B
Rao<bharata@linux.vnet.ibm.com> wrote:
> - Hard limits can be used to provide guarantees.
>
This claim (and the subsequent long thread it generated on how limits
can provide guarantees) confused me a bit.
Why do we need limits to provide guarantees when we can already
provide guarantees via shares?
Suppose 10 cgroups each want 10% of the machine's CPU. We can just
give each cgroup an equal share, and they're guaranteed 10% if they
try to use it; if they don't use it, other cgroups can get access to
the idle cycles.
Suppose cgroup A wants a guarantee of 50% and two others, B and C,
want guarantees of 15% each; give A 50 shares and B and C 15 shares
each. In this case, if they all run flat out they'll get 62%/19%/19%,
which is within their SLA.
That's not to say that hard limits can't be useful in their own right
- e.g. for providing reproducible loadtesting conditions by
controlling how much CPU a service can use during the load test. But I
don't see why using them to implement guarantees is either necessary
or desirable.
(Unless I'm missing some crucial point ...)
Paul
next prev parent reply other threads:[~2009-06-05 8:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 5:36 Bharata B Rao
2009-06-04 12:19 ` Avi Kivity
2009-06-04 21:32 ` Mike Waychison
2009-06-05 3:03 ` Bharata B Rao
2009-06-05 3:33 ` Avi Kivity
2009-06-05 4:37 ` Balbir Singh
2009-06-05 4:44 ` Avi Kivity
2009-06-05 4:49 ` Balbir Singh
2009-06-05 5:09 ` Chris Friesen
2009-06-05 5:13 ` Balbir Singh
2009-06-05 5:10 ` Balbir Singh
2009-06-05 5:21 ` Avi Kivity
2009-06-05 5:27 ` Balbir Singh
2009-06-05 5:31 ` Bharata B Rao
2009-06-05 6:01 ` Avi Kivity
2009-06-05 8:16 ` Bharata B Rao
2009-06-07 6:04 ` Avi Kivity
2009-06-07 16:14 ` Bharata B Rao
2009-06-05 9:39 ` Balbir Singh
2009-06-05 13:14 ` Avi Kivity
2009-06-05 13:42 ` Balbir Singh
2009-06-07 6:09 ` Avi Kivity
2009-06-05 14:54 ` Chris Friesen
2009-06-07 6:10 ` Avi Kivity
2009-06-05 9:24 ` Balbir Singh
2009-06-05 6:03 ` Avi Kivity
2009-06-05 6:32 ` Bharata B Rao
2009-06-05 12:57 ` Avi Kivity
2009-06-05 5:16 ` Avi Kivity
2009-06-05 5:20 ` Balbir Singh
2009-06-05 3:07 ` Balbir Singh
2009-06-05 8:53 ` Paul Menage [this message]
2009-06-05 9:27 ` Bharata B Rao
2009-06-05 9:32 ` Paul Menage
2009-06-05 9:48 ` Dhaval Giani
2009-06-05 9:51 ` Paul Menage
2009-06-05 9:59 ` Dhaval Giani
2009-06-05 10:03 ` Paul Menage
2009-06-08 8:50 ` Pavel Emelyanov
2009-06-05 9:36 ` Balbir Singh
2009-06-05 9:48 ` Paul Menage
2009-06-05 9:55 ` Balbir Singh
2009-06-05 9:57 ` Paul Menage
2009-06-05 10:02 ` Paul Menage
2009-06-05 11:32 ` Srivatsa Vaddagiri
2009-06-05 12:18 ` Paul Menage
2009-06-07 10:11 ` Srivatsa Vaddagiri
2009-06-07 15:35 ` Balbir Singh
2009-06-08 4:37 ` Srivatsa Vaddagiri
2009-06-05 14:44 ` Chris Friesen
2009-06-05 13:02 ` Avi Kivity
2009-06-05 13:43 ` Dhaval Giani
2009-06-05 14:45 ` Chris Friesen
2009-06-05 9:02 ` Reinhard Tartler
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=6599ad830906050153i1afd104fqe70f681317349142@mail.gmail.com \
--to=menage@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=herbert@13thfloor.at \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=svaidy@linux.vnet.ibm.com \
--cc=vatsa@in.ibm.com \
--cc=xemul@openvz.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
all inboxes | Powered by JetHome®