mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryo Tsuruta <ryov@valinux.co.jp>
To: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	containers@lists.linux-foundation.org,
	virtualization@lists.linux-foundation.org,
	xen-devel@lists.xensource.com
Subject: [PATCH 7/9] blkio-cgroup-v13: The document of blkio-cgroup
Date: Fri, 02 Oct 2009 20:58:43 +0900 (JST)	[thread overview]
Message-ID: <20091002.205843.183050041.ryov@valinux.co.jp> (raw)
In-Reply-To: <20091002.205817.112597159.ryov@valinux.co.jp>

The document of blkio-cgroup.

Signed-off-by: Hirokazu Takahashi <taka@valinux.co.jp>
Signed-off-by: Ryo Tsuruta <ryov@valinux.co.jp>

---
 Documentation/cgroups/00-INDEX  |    2 +
 Documentation/cgroups/blkio.txt |   49 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 51 insertions(+)

Index: linux-2.6.32-rc1/Documentation/cgroups/00-INDEX
===================================================================
--- linux-2.6.32-rc1.orig/Documentation/cgroups/00-INDEX
+++ linux-2.6.32-rc1/Documentation/cgroups/00-INDEX
@@ -16,3 +16,5 @@ memory.txt
 	- Memory Resource Controller; design, accounting, interface, testing.
 resource_counter.txt
 	- Resource Counter API.
+blkio.txt
+	- Block I/O Tracking; description, interface and examples.
Index: linux-2.6.32-rc1/Documentation/cgroups/blkio.txt
===================================================================
--- /dev/null
+++ linux-2.6.32-rc1/Documentation/cgroups/blkio.txt
@@ -0,0 +1,49 @@
+Block I/O Cgroup
+
+1. Overview
+
+Using this feature the owners of any type of I/O can be determined.
+This allows dm-ioband to control block I/O bandwidth even when it is
+accepting delayed write requests. dm-ioband can find the cgroup of
+each request. It is also for possible that others working on I/O
+bandwidth throttling to use this functionality to control asynchronous
+I/O with a little enhancement.
+
+2. Setting up blkio-cgroup
+
+The following kernel config options are required.
+
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_BLKIO=y
+
+Selecting the options for the cgroup memory subsystem is also recommended
+as it makes it possible to give some I/O bandwidth and memory to a selected
+cgroup to control delayed write requests. The amount of dirty pages is
+limited within the cgroup even if the allocated bandwidth is narrow.
+
+CONFIG_RESOURCE_COUNTERS=y
+CONFIG_CGROUP_MEM_RES_CTLR=y
+
+3. User interface
+
+3.1 Mounting the cgroup filesystem
+
+First, mount the cgroup filesystem in order to enable observation and
+modification of the blkio-cgroup settings.
+
+# mount -t cgroup -o blkio none /cgroup
+
+3.2 The blkio.id file
+
+After mounting the cgroup filesystem the blkio.id file will be visible
+in the cgroup directory. This file contains a unique ID number for
+each cgroup. When an I/O operation starts, blkio-cgroup sets the
+page's ID number on the page cgroup. The cgroup of I/O can be
+determined by retrieving the ID number from the page cgroup, because
+the page cgroup is associated with the page which is involved in the
+I/O.
+
+4. Contact
+
+Linux Block I/O Bandwidth Control Project
+http://sourceforge.net/projects/ioband/

  reply	other threads:[~2009-10-02 11:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 11:56 [PATCH 1/9] I/O bandwidth controller and BIO tracking Ryo Tsuruta
2009-10-02 11:56 ` [PATCH 2/9] dm-ioband-1.14.0: All-in-one patch Ryo Tsuruta
2009-10-02 11:57   ` [PATCH 3/9] blkio-cgroup-v13: The new page_cgroup framework Ryo Tsuruta
2009-10-02 11:57     ` [PATCH 4/9] blkio-cgroup-v13: Refactoring io-context initialization Ryo Tsuruta
2009-10-02 11:57       ` [PATCH 5/9] blkio-cgroup-v13: The body of blkio-cgroup Ryo Tsuruta
2009-10-02 11:58         ` [PATCH 6/9] blkio-cgroup-v13: Page tracking hooks Ryo Tsuruta
2009-10-02 11:58           ` Ryo Tsuruta [this message]
2009-10-02 11:59             ` [PATCH 8/9] blkio-cgroup-v13: Add a cgroup support to dm-ioband Ryo Tsuruta
2009-10-02 11:59               ` [PATCH 9/9] blkio-cgroup-v13: The document of a cgroup support for dm-ioband Ryo Tsuruta

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=20091002.205843.183050041.ryov@valinux.co.jp \
    --to=ryov@valinux.co.jp \
    --cc=containers@lists.linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.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®