[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ACCC4B7.4050805@redhat.com>
Date: Wed, 07 Oct 2009 12:41:27 -0400
From: Rik van Riel <riel@...hat.com>
To: Ryo Tsuruta <ryov@...inux.co.jp>
CC: vgoyal@...hat.com, nauman@...gle.com, m-ikeda@...jp.nec.com,
linux-kernel@...r.kernel.org, jens.axboe@...cle.com,
containers@...ts.linux-foundation.org, dm-devel@...hat.com,
dpshah@...gle.com, lizf@...fujitsu.com, mikew@...gle.com,
fchecconi@...il.com, paolo.valente@...more.it,
fernando@....ntt.co.jp, s-uchida@...jp.nec.com, taka@...inux.co.jp,
guijianfeng@...fujitsu.com, jmoyer@...hat.com,
dhaval@...ux.vnet.ibm.com, balbir@...ux.vnet.ibm.com,
righi.andrea@...il.com, agk@...hat.com, akpm@...ux-foundation.org,
peterz@...radead.org, jmarchan@...hat.com,
torvalds@...ux-foundation.org, mingo@...e.hu,
yoshikawa.takuya@....ntt.co.jp
Subject: Re: IO scheduler based IO controller V10
Ryo Tsuruta wrote:
> If once dm-ioband is integrated into the LVM tools and bandwidth can
> be assigned per device by lvcreate, the use of dm-tools is no longer
> required for users.
A lot of large data center users have a SAN, with volume management
handled SAN-side and dedicated LUNs for different applications or
groups of applications.
Because of alignment issues, they typically use filesystems directly
on top of the LUNs, without partitions or LVM layers. We cannot rely
on LVM for these systems, because people prefer not to use that.
Besides ... isn't the goal of the cgroups io bandwidth controller
to control the IO used by PROCESSES?
If we want to control processes, why would we want the configuration
to be applied to any other kind of object in the system?
--
All rights reversed.
--
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