[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090417.163208.39173254.ryov@valinux.co.jp>
Date: Fri, 17 Apr 2009 16:32:08 +0900 (JST)
From: Ryo Tsuruta <ryov@...inux.co.jp>
To: yoshikawa.takuya@....ntt.co.jp
Cc: righi.andrea@...il.com, menage@...gle.com,
balbir@...ux.vnet.ibm.com, guijianfeng@...fujitsu.com,
kamezawa.hiroyu@...fujitsu.com, agk@...rceware.org,
akpm@...ux-foundation.org, axboe@...nel.dk, baramsori72@...il.com,
chlunde@...g.uio.no, dave@...ux.vnet.ibm.com, dpshah@...gle.com,
eric.rannaud@...il.com, fernando@....ntt.co.jp, taka@...inux.co.jp,
lizf@...fujitsu.com, matt@...ehost.com, dradford@...ehost.com,
ngupta@...gle.com, randy.dunlap@...cle.com, roberto@...it.it,
s-uchida@...jp.nec.com, subrata@...ux.vnet.ibm.com,
containers@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/9] bio-cgroup controller
Hi,
From: Takuya Yoshikawa <yoshikawa.takuya@....ntt.co.jp>
Subject: Re: [PATCH 3/9] bio-cgroup controller
Date: Fri, 17 Apr 2009 10:49:43 +0900
> > +config CGROUP_BIO
> > + bool "Block I/O cgroup subsystem"
> > + depends on CGROUPS && BLOCK
> > + select MM_OWNER
> > + help
> > + Provides a Resource Controller which enables to track the onwner
> > + of every Block I/O requests.
> > + The information this subsystem provides can be used from any
> > + kind of module such as dm-ioband device mapper modules or
> > + the cfq-scheduler.
>
>o I can understand this kind of information will be effective for io
> controllers but how about cfq-scheduler? Don't we need some changes to
> make cfq use this kind of information?
You need to modify cfq-scheduler to use bio-cgruop.
Thanks,
Ryo Tsuruta
--
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