From: Divyesh Shah <dpshah@google.com>
To: Andrea Righi <righi.andrea@gmail.com>,
balbir@linux.vnet.ibm.com, menage@google.com
Cc: linux-kernel@vger.kernel.org, axboe@kernel.dk, matt@bluehost.com,
roberto@unbit.it, randy.dunlap@oracle.com,
akpm@linux-foundation.org
Subject: Re: i/o bandwidth controller infrastructure
Date: Mon, 16 Jun 2008 13:51:34 -0700 [thread overview]
Message-ID: <48D0786A-AC3B-46C3-B35C-EAAA47BFAEBC@google.com> (raw)
In-Reply-To: <75b07c02-1595-4af2-ac87-3b067459f62e@w8g2000prd.googlegroups.com>
>
> This is the core io-throttle kernel infrastructure. It creates the
> basic
> interfaces to cgroups and implements the I/O measurement and
> throttling
> functions.
I am not sure if throttling an application's cpu usage by explicitly
putting it to sleep
in order to restrain it from making more IO requests is the way to go
here (though I can't think
of anything better right now).
With this bandwidth controller, a cpu-intensive job which otherwise
does not care about its IO
performance needs to be pin-point accurate about IO bandwidth
required in order to not suffer
from cpu-throttling. IMHO, if a cgroup is exceeding its limit for a
given resource, the throttling
should be done _only_ for that resource.
-Divyesh
next parent reply other threads:[~2008-06-16 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030410181011$6d15@gated-at.bofh.it>
[not found] ` <aC1Yl-2AL-1@gated-at.bofh.it>
[not found] ` <75b07c02-1595-4af2-ac87-3b067459f62e@w8g2000prd.googlegroups.com>
2008-06-16 20:51 ` Divyesh Shah [this message]
2008-06-16 22:39 ` Andrea Righi
2008-06-22 19:41 ` Eric Rannaud
2008-06-23 10:37 ` Andrea Righi
[not found] ` <aXrl4-2FX-1@gated-at.bofh.it>
2008-08-09 14:08 ` [PATCH 1/1] [x86] Configuration options to compile out x86 CPU support code Bodo Eggert
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=48D0786A-AC3B-46C3-B35C-EAAA47BFAEBC@google.com \
--to=dpshah@google.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@bluehost.com \
--cc=menage@google.com \
--cc=randy.dunlap@oracle.com \
--cc=righi.andrea@gmail.com \
--cc=roberto@unbit.it \
/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®