From: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
To: Vivek Goyal <vgoyal@redhat.com>, Jens Axboe <axboe@kernel.dk>
Cc: Nauman Rafique <nauman@google.com>,
Chad Talbott <ctalbott@google.com>,
Divyesh Shah <dpshah@google.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Subject: [PATCH 4/4] blkio-cgroup: Documents for use_hierarchy interface
Date: Thu, 21 Oct 2010 10:37:38 +0800 [thread overview]
Message-ID: <4CBFA772.7000702@cn.fujitsu.com> (raw)
In-Reply-To: <4CBFA64D.6050800@cn.fujitsu.com>
Documents for use_hierarchy interface.
Signed-off-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
---
Documentation/cgroups/blkio-controller.txt | 21 +++++++++++++++++++++
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/Documentation/cgroups/blkio-controller.txt b/Documentation/cgroups/blkio-controller.txt
index d6da611..df6c938 100644
--- a/Documentation/cgroups/blkio-controller.txt
+++ b/Documentation/cgroups/blkio-controller.txt
@@ -15,6 +15,21 @@ one is throttling policy which can be used to specify upper IO rate limits
on devices. This policy is implemented in generic block layer and can be
used on leaf nodes as well as higher level logical devices like device mapper.
+Currently, both hierarchical bandwidth division and flat bandwidth division are
+supported. Consider the follow hierarchy:
+
+ grp1
+ / \
+ grp2 grp3
+ / \
+ grp4 grp5
+
+All groups have a same weight 500, and only grp3 grp4 and grp5 are contending
+for IO bandwidth. If flat bandwidth division is in use, grp3 grp4 and grp5 will
+share the same bandwidth, that is 33.3% for each. If hierarchical bandwidth
+division is in use, grp4 and grp5 will get 25% of bandwidth for each, gpr3
+will get the reset 50%.
+
HOWTO
=====
Proportional Weight division of bandwidth
@@ -142,6 +157,12 @@ Proportional weight policy files
dev weight
8:16 300
+- blkio.use_hierarchy
+ - If this interface is set, hierarchical bandwidth division is enabled.
+ Ohterwise, flat bandwidth division is enabled. Currently this
+ interface only shows up in root cgroup, and works in the case that
+ there're no child cgroups.
+
- blkio.time
- disk time allocated to cgroup per device in milliseconds. First
two fields specify the major and minor number of the device and
-- 1.6.5.2
prev parent reply other threads:[~2010-10-21 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 2:32 [RFC] [PATCH 0/4] cfq-iosched: Enable hierarchical cfq group scheduling and add use_hierarchy interface Gui Jianfeng
2010-10-21 2:34 ` [PATCH 1/4 v2] cfq-iosched: add cfq group hierarchical scheduling support Gui Jianfeng
2010-10-22 20:54 ` Vivek Goyal
2010-10-22 21:11 ` Vivek Goyal
2010-10-25 2:48 ` Gui Jianfeng
2010-10-25 20:20 ` Vivek Goyal
2010-10-26 2:15 ` Gui Jianfeng
2010-10-26 15:57 ` Vivek Goyal
2010-10-27 1:29 ` Gui Jianfeng
2010-10-21 2:36 ` [PATCH 2/4] blkio-cgroup: Add a new interface use_hierarchy Gui Jianfeng
2010-10-21 2:36 ` [PATCH 3/4] cfq-iosched: Enable both hierarchical mode and flat mode for cfq group scheduling Gui Jianfeng
2010-10-21 2:37 ` Gui Jianfeng [this message]
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=4CBFA772.7000702@cn.fujitsu.com \
--to=guijianfeng@cn.fujitsu.com \
--cc=axboe@kernel.dk \
--cc=ctalbott@google.com \
--cc=dpshah@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nauman@google.com \
--cc=vgoyal@redhat.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