[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <48C776B0.9070703@gmail.com>
Date: Wed, 10 Sep 2008 09:26:40 +0200
From: Andrea Righi <righi.andrea@...il.com>
To: Dave Hansen <dave@...ux.vnet.ibm.com>
CC: Balbir Singh <balbir@...ux.vnet.ibm.com>,
Paul Menage <menage@...gle.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
David Radford <dradford@...ehost.com>,
Marco Innocenti <m.innocenti@...eca.it>,
Fernando Luis Vázquez Cao
<fernando@....ntt.co.jp>, containers@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>,
Carl Henrik Lunde <chlunde@...g.uio.no>, linux-mm@...ck.org,
Divyesh Shah <dpshah@...gle.com>,
Matt Heaton <matt@...ehost.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Naveen Gupta <ngupta@...gle.com>
Subject: Re: [RFC] [PATCH -mm] cgroup: limit the amount of dirty file pages
Dave Hansen wrote:
> On Tue, 2008-09-09 at 17:38 +0200, Andrea Righi wrote:
>> It allows to control how much dirty file pages a cgroup can have at any
>> given time. This feature is supposed to be strictly connected to a
>> generic cgroup IO controller (see below).
>
> So, this functions similarly to our global dirty ratio? Is it just
> intended to keep a cgroup from wedging itself too hard with too many
> dirty pages, just like the global ratio?
>
> -- Dave
Correct, it's the same functionality provided by vm.dirty_ratio and
vm.dirty_background_ratio, except that is intended to be per-cgroup.
Without this functionality, a cgroup can even dirty all its memory,
allocated by the memory controller, since statistics and writeback
configurations are global.
-Andrea
--
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