From mboxrd@z Thu Jan 1 00:00:00 1970 From: KAMEZAWA Hiroyuki Subject: Re: IO controller discussion (Was: Re: [PATCH 01/10] Documentation) Date: Tue, 21 Apr 2009 10:16:17 +0900 Message-ID: <20090421101617.27d62587.kamezawa.hiroyu__45914.1698935584$1240276991$gmane$org@jp.fujitsu.com> References: <20090312001146.74591b9d.akpm@linux-foundation.org> <20090312180126.GI10919@redhat.com> <49D8CB17.7040501@gmail.com> <20090407064046.GB20498@redhat.com> <20090408203756.GB10077@linux> <20090416183753.GE8896@redhat.com> <20090417093656.GA5246@linux> <20090417141358.GD29086@redhat.com> <661de9470904180619k34e7998ch755a2ad3bed9ce5e@mail.gmail.com> <20090419134508.GG8493@redhat.com> <20090419155358.GC5514@linux> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090419155358.GC5514@linux> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Andrea Righi Cc: paolo.valente-rcYM44yAMweonA0d6jMUrA@public.gmane.org, fernando-w0OK63jvRlAuJ+9fw/WgBHgSJqDPrsil@public.gmane.org, dhaval-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org, containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, oz-kernel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, fchecconi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, arozansk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, jens.axboe-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org, Andrew Morton , menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, Balbir Singh List-Id: containers.vger.kernel.org On Sun, 19 Apr 2009 17:53:59 +0200 Andrea Righi wrote: > > > > Got a question for you. Does memory controller already have the per cgroup > > dirty pages limit? If no, has this been discussed in the past? if yes, > > what was the conclsion? > IMHO, dirty page handling and I/O throttling is a different problem. - A task (or cgroup) which makes the page dirty and - A task (or cgroup) to which a page is accounted Is different from each other, in general. I have a plan to add dirty_ratio to memcg, but it's for avoiding massive stavation in memory reclaim, not for I/O control. If you want to implement I/O throttle in MM layer, plz don't depend on memcg. The perpose is different. Thanks, -Kame