linux-kernel - [PATCH -mm 0/3] cgroup: block device i/o bandwidth controller (v5)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1215862291-26719-1-git-send-email-righi.andrea@gmail.com>
Date:	Sat, 12 Jul 2008 13:31:28 +0200
From:	Andrea Righi <righi.andrea@...il.com>
To:	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Paul Menage <menage@...gle.com>, akpm@...ux-foundation.org
Cc:	Li Zefan <lizf@...fujitsu.com>,
	Carl Henrik Lunde <chlunde@...g.uio.no>, axboe@...nel.dk,
	matt@...ehost.com, roberto@...it.it, randy.dunlap@...cle.com,
	Divyesh Shah <dpshah@...gle.com>, subrata@...ux.vnet.ibm.com,
	eric.rannaud@...il.com, containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: [PATCH -mm 0/3] cgroup: block device i/o bandwidth controller (v5)


The objective of the i/o bandwidth 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 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.26-rc8-mm1.

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

Thanks to Li Zefan for reviewing.

Changelog: (v4 -> v5)
  - rebase to 2.6.26-rc8-mm1
  - handle AIO opportunely: return -EAGAIN from sys_io_submit(), instead of
    making to sleep tasks doing AIO
  - userspace=>kernel interface now accepts the following syntaxes:
    * dev:0                       <- to delete a limiting rule
    * dev:bw-limit:0              <- define a leaky bucket throttling rule
    * dev:bw-limit:1:bucket-size  <- define a token bucket throttling rule
  - use .write_string and .read_seq_string to simplify iothrottle_read() and
    iothrottle_write() functions
  - use a enum structure to enumerate the various throttling algorithms

TODO:
  - see documentation

-Andrea
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/