[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081110134407.GA26956@redhat.com>
Date: Mon, 10 Nov 2008 08:44:07 -0500
From: Vivek Goyal <vgoyal@...hat.com>
To: Li Zefan <lizf@...fujitsu.com>
Cc: linux-kernel@...r.kernel.org,
containers@...ts.linux-foundation.org,
virtualization@...ts.linux-foundation.org, jens.axboe@...cle.com,
Hirokazu Takahashi <taka@...inux.co.jp>,
Ryo Tsuruta <ryov@...inux.co.jp>,
Andrea Righi <righi.andrea@...il.com>,
Satoshi UCHIDA <s-uchida@...jp.nec.com>,
fernando@....ntt.co.jp, balbir@...ux.vnet.ibm.com,
Andrew Morton <akpm@...ux-foundation.org>, menage@...gle.com,
ngupta@...gle.com, Rik van Riel <riel@...hat.com>,
Jeff Moyer <jmoyer@...hat.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [patch 1/4] io controller: documentation
On Mon, Nov 10, 2008 at 10:48:54AM +0800, Li Zefan wrote:
> Hi, Vivek
>
> Thanks for your work. :)
>
> A question below.
>
> > +For example, assume there are two cgroups A and B with weights 1024 and 2048
> > +in the system. Tasks in two cgroups A and B are doing IO to two disks sda and
> > +sdb in the system. A user has enabled IO control on both sda and sdb. Now on
> > +both sda and sdb, tasks in cgroup B will get to use 2/3 of disk BW and
> > +tasks in cgroup A will get to use 1/3 of disk bandwidth, only in case of
> > +contention. If tasks in any of the groups stop doing IO to a particular disk,
> > +task in other group will get to use full disk BW for that duration.
> > +
>
> So in this example, I can't assign 1/3 of sda's disk BW while 2/3 of sdb's
> disk BW to A. Am I right?
Hi,
Yes you are right. Currently policies are global and not per disk. So in
above example, cgroup A will get 1/3 of disk BW both on sda and sdb. And
one can not configure in such a manner so that A gets 1/3 of BW on sda and
2/3 of BW on sdb.
I think assigning cgroup weights per disk should be doable but personally
I think it makes configuration complex and I am not sure if it really a
very useful feature.
Thanks
Vivek
--
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/
Powered by blists - more mailing lists