mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Righi <righi.andrea@gmail.com>
To: balbir@linux.vnet.ibm.com, menage@google.com
Cc: matt@bluehost.com, roberto@unbit.it, randy.dunlap@oracle.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] cgroup: block device i/o bandwidth controller (v2)
Date: Sat,  7 Jun 2008 00:27:27 +0200	[thread overview]
Message-ID: <1212791250-32320-1-git-send-email-righi.andrea@gmail.com> (raw)
In-Reply-To: <>


The goal of the i/o bandwidth controller is to improve i/o performance
predictability and provide better QoS for 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 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 latest git (2.6.26-rc5).

The all-in-one patch can be found at:
http://download.systemimager.org/~arighi/linux/patches/io-throttle/

Previous version and test report can be found here:
http://lkml.org/lkml/2008/5/24/97

Changelog since v1:
* support multiple per-block device i/o limiting rules
* minor optimizations in cgroup_io_account()
* updated the documentation and fixed some typos (thanks to Randy Dunlap for
  reviewing)

-Andrea

             reply	other threads:[~2008-06-07  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 22:27 Andrea Righi [this message]
2008-06-10  5:14 ` 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=1212791250-32320-1-git-send-email-righi.andrea@gmail.com \
    --to=righi.andrea@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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=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®