From: Andrea Righi <righi.andrea@gmail.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>,
Paul Menage <menage@google.com>
Cc: akpm@linux-foundation.org, Li Zefan <lizf@cn.fujitsu.com>,
Carl Henrik Lunde <chlunde@ping.uio.no>,
axboe@kernel.dk, matt@bluehost.com, roberto@unbit.it,
Marco Innocenti <m.innocenti@cineca.it>,
randy.dunlap@oracle.com, Divyesh Shah <dpshah@google.com>,
subrata@linux.vnet.ibm.com, eric.rannaud@gmail.com,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm 0/3] cgroup: block device i/o controller (v8)
Date: Mon, 4 Aug 2008 00:14:55 +0200 [thread overview]
Message-ID: <1217801698-13438-1-git-send-email-righi.andrea@gmail.com> (raw)
In-Reply-To: <>
The objective of the i/o controller is to improve i/o performance
predictability of different cgroups sharing the same block devices.
Respect to other priority/weight-based solutions the approach used by this
controller is to explicitly choke applications' requests that directly (or
indirectly) generate i/o activity in the system.
The direct bandwidth and/or iops limiting method has the advantage of improving
the performance predictability at the cost of reducing, in general, the overall
performance of the system (in terms of throughput).
Detailed informations about design, its goal and usage are described in the
documentation.
Tested against 2.6.27-rc1-mm1.
The all-in-one patch (and previous versions) can be found at:
http://download.systemimager.org/~arighi/linux/patches/io-throttle/
Changelog: (v7 -> v8)
- rebase to 2.6.27-rc1-mm1
- implement token bucket iops/s throttling
- in the cgroup filesystem blockio.bandwidth has been renamed to
blockio.bandwidth-max and blockio.iops to blockio.iops-max
(for the future we would like to have also blockio.bandwidth-min and
blockio.iops-min and implement a mechanism to guarantee minimum performance
levels as well)
- token bucket rules can also be defined using the syntax:
DEV:LIMIT:1 (instead of DEV:LIMIT:1:BUCKET-SIZE)
In this case BUCKET-SIZE will be set equal to LIMIT (this is valid both for
I/O bandwidth limiting and I/O operations limiting rules)
- updated documentation
-Andrea
reply other threads:[~2008-08-03 22:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1217801698-13438-1-git-send-email-righi.andrea@gmail.com \
--to=righi.andrea@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=balbir@linux.vnet.ibm.com \
--cc=chlunde@ping.uio.no \
--cc=containers@lists.linux-foundation.org \
--cc=dpshah@google.com \
--cc=eric.rannaud@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=m.innocenti@cineca.it \
--cc=matt@bluehost.com \
--cc=menage@google.com \
--cc=randy.dunlap@oracle.com \
--cc=roberto@unbit.it \
--cc=subrata@linux.vnet.ibm.com \
/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®