From: Vivek Goyal <vgoyal@redhat.com>
To: Jens Axboe <jaxboe@fusionio.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Gui Jianfeng <guijianfeng@cn.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Nauman Rafique <nauman@google.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [RFC] blk-cgroup: Allow creation of hierarchical cgroups
Date: Mon, 15 Nov 2010 10:28:32 -0500 [thread overview]
Message-ID: <20101115152832.GH30792@redhat.com> (raw)
In-Reply-To: <20101102222030.GI7198@redhat.com>
On Tue, Nov 02, 2010 at 06:20:30PM -0400, Vivek Goyal wrote:
> o Allow hierarchical cgroup creation for blkio controller
>
> o Currently we disallow it as both the io controller policies (throttling
> as well as proportion bandwidth) do not support hierarhical accounting
> and control. But the flip side is that blkio controller can not be used with
> libvirt as libvirt creates a cgroup hierarchy deeper than 1 level.
>
> <top-level-cgroup-dir>/<controller>/libvirt/qemu/<virtual-machine-groups>
>
> o So this patch will allow creation of cgroup hierarhcy but at the backend
> everything will be treated as flat. So if somebody created a an hierarchy
> like as follows.
>
> root
> / \
> test1 test2
> |
> test3
>
> CFQ and throttling will practically treat all groups at same level.
>
> pivot
> / | \ \
> root test1 test2 test3
>
> o Once we have actual support for hierarchical accounting and control
> then we can introduce another cgroup tunable file "blkio.use_hierarchy"
> which will be 0 by default but if user wants to enforce hierarhical
> control then it can be set to 1. This way there should not be any
> ABI problems down the line.
>
> o The only not so pretty part is introduction of extra file "use_hierarchy"
> down the line. Kame-san had mentioned that hierarhical accounting is
> expensive in memory controller hence they keep it off by default. I
> suspect same will be the case for IO controller also as for each IO
> completion we shall have to account IO through hierarchy up to the root.
> if yes, then it probably is not a very bad idea to introduce this extra
> file so that it will be used only when somebody needs it and some people
> might enable hierarchy only in part of the hierarchy.
>
> o This is how basically memory controller also uses "use_hierarhcy" and
> they also allowed creation of hierarchies when actual backend support
> was not available.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
> ---
Hi Jens,
Do you have any concerns about this patch? If not, can you please apply
it.
Thanks
Vivek
> Documentation/cgroups/blkio-controller.txt | 27 +++++++++++++++++++++++++++
> block/blk-cgroup.c | 4 ----
> 2 files changed, 27 insertions(+), 4 deletions(-)
>
> Index: linux-2.6/block/blk-cgroup.c
> ===================================================================
> --- linux-2.6.orig/block/blk-cgroup.c 2010-10-28 14:19:02.000000000 -0400
> +++ linux-2.6/block/blk-cgroup.c 2010-11-02 13:10:13.000000000 -0400
> @@ -1452,10 +1452,6 @@ blkiocg_create(struct cgroup_subsys *sub
> goto done;
> }
>
> - /* Currently we do not support hierarchy deeper than two level (0,1) */
> - if (parent != cgroup->top_cgroup)
> - return ERR_PTR(-EPERM);
> -
> blkcg = kzalloc(sizeof(*blkcg), GFP_KERNEL);
> if (!blkcg)
> return ERR_PTR(-ENOMEM);
> Index: linux-2.6/Documentation/cgroups/blkio-controller.txt
> ===================================================================
> --- linux-2.6.orig/Documentation/cgroups/blkio-controller.txt 2010-10-28 14:19:01.000000000 -0400
> +++ linux-2.6/Documentation/cgroups/blkio-controller.txt 2010-11-02 17:51:52.000000000 -0400
> @@ -89,6 +89,33 @@ Throttling/Upper Limit policy
>
> Limits for writes can be put using blkio.write_bps_device file.
>
> +Hierarchical Cgroups
> +====================
> +- Currently none of the IO control policy supports hierarhical groups. But
> + cgroup interface does allow creation of hierarhical cgroups and internally
> + IO policies treat them as flat hierarchy.
> +
> + So this patch will allow creation of cgroup hierarhcy but at the backend
> + everything will be treated as flat. So if somebody created a hierarchy like
> + as follows.
> +
> + root
> + / \
> + test1 test2
> + |
> + test3
> +
> + CFQ and throttling will practically treat all groups at same level.
> +
> + pivot
> + / | \ \
> + root test1 test2 test3
> +
> + Down the line we can implement hierarchical accounting/control support
> + and also introduce a new cgroup file "use_hierarchy" which will control
> + whether cgroup hierarchy is viewed as flat or hierarchical by the policy.
> + This is how memory controller also has implemented the things.
> +
> Various user visible config options
> ===================================
> CONFIG_BLK_CGROUP
next prev parent reply other threads:[~2010-11-15 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 22:20 [RFC] blk-cgroup: Allow creation of hierarchical cgroups Vivek Goyal
2010-11-03 0:11 ` Chad Talbott
2010-11-03 13:26 ` Vivek Goyal
2010-11-03 2:27 ` Balbir Singh
2010-11-03 4:14 ` Gui Jianfeng
2010-11-03 15:03 ` Ciju Rajan K
2010-11-15 15:28 ` Vivek Goyal [this message]
2010-11-15 18:38 ` Jens Axboe
2010-11-16 2:50 ` KAMEZAWA Hiroyuki
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=20101115152832.GH30792@redhat.com \
--to=vgoyal@redhat.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jaxboe@fusionio.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=nauman@google.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;
as well as URLs for NNTP newsgroup(s).