linux-kernel - [PATCH 0/4] io-controller: Use names rather than major:minor

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>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Mar 2010 11:04:17 -0700
From:	Chad Talbott <ctalbott@...gle.com>
To:	vgoyal@...hat.com, jens.axboe@...cle.com
Cc:	mrubin@...gle.com, guijianfeng@...fujitsu.com,
	Li Zefan <lizf@...fujitsu.com>, linux-kernel@...r.kernel.org,
	dpshah@...gle.com, Nauman Rafique <nauman@...gle.com>
Subject: [PATCH 0/4] io-controller: Use names rather than major:minor

This stack (which includes Gui's patch for per-device weights),
changes the various blkio.* stats to use the disks' names (sda, sdb,
etc.) rather than major:minor pairs when printing statistics.
Additionally setting a per-device policy can be done via the disk's
name.

This has the side effect of fixing the "root cgroup shows no stats"
problem that Ricky mentioned.

Chad

---

Chad Talbott (4):
      blkio_group key change: void * -> request_queue *
      Adds an RCU-protected pointer to request_queue that makes it easy to
      io-controller: Add a new interface "weight_device" for IO-Controller
      Use disk-names to set blkio.weight_device policy


 block/blk-cgroup.c     |  224 +++++++++++++++++++++++++++++++++++++++++++++---
 block/blk-cgroup.h     |   23 ++++-
 block/blk-sysfs.c      |    4 +
 block/cfq-iosched.c    |   27 ++----
 include/linux/blkdev.h |    6 +
 5 files changed, 248 insertions(+), 36 deletions(-)

--
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/