From: "Paul Menage" <menage@google.com>
To: "Dhaval Giani" <dhaval@linux.vnet.ibm.com>
Cc: "Andrea Righi" <righiandr@users.sourceforge.net>,
"Balbir Singh" <balbir@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cgroup: limit block I/O bandwidth
Date: Fri, 18 Jan 2008 07:41:03 -0500 [thread overview]
Message-ID: <6599ad830801180441o2d60ffc9s47de9362cda40282@mail.gmail.com> (raw)
In-Reply-To: <20080118123605.GB14339@linux.vnet.ibm.com>
On Jan 18, 2008 7:36 AM, Dhaval Giani <dhaval@linux.vnet.ibm.com> wrote:
> On Fri, Jan 18, 2008 at 12:41:03PM +0100, Andrea Righi wrote:
> > Allow to limit the block I/O bandwidth for specific process containers
> > (cgroups) imposing additional delays on I/O requests for those processes
> > that exceed the limits defined in the control group filesystem.
> >
> > Example:
> > # mkdir /dev/cgroup
> > # mount -t cgroup -oio-throttle io-throttle /dev/cgroup
>
> Just a minor nit, can't we name it as io, keeping in mind that other
> controllers are known as cpu and memory?
Or maybe "blockio"?
Paul
next prev parent reply other threads:[~2008-01-18 12:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 11:41 [PATCH] cgroup: limit block I/O bandwidth Andrea Righi
2008-01-18 12:36 ` Dhaval Giani
2008-01-18 12:41 ` Paul Menage [this message]
2008-01-18 13:02 ` Andrea Righi
2008-01-18 15:50 ` Andrea Righi
2008-01-18 22:39 Naveen Gupta
2008-01-19 11:17 ` Andrea Righi
2008-01-20 13:45 ` Andrea Righi
2008-01-20 14:32 ` Jens Axboe
2008-01-20 14:58 ` Balbir Singh
2008-01-20 15:41 ` Andrea Righi
2008-01-20 16:06 ` Jens Axboe
2008-01-20 23:59 ` Andrea Righi
2008-01-22 19:02 ` Naveen Gupta
2008-01-22 23:11 ` Andrea Righi
2008-01-23 1:17 ` Naveen Gupta
2008-01-23 15:23 ` Andrea Righi
2008-01-23 15:38 ` Balbir Singh
2008-01-23 20:55 ` Andrea Righi
2008-01-24 9:05 ` Pavel Emelyanov
2008-01-24 13:48 ` Andrea Righi
2008-01-24 13:50 ` Balbir Singh
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=6599ad830801180441o2d60ffc9s47de9362cda40282@mail.gmail.com \
--to=menage@google.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=righiandr@users.sourceforge.net \
/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 NNTP newsgroup(s).