[PATCH v3 11/11] memcg: check memcg dirty limits in page writeback
kamezawa.hiroyu at jp.fujitsu.com
Tue Oct 19 21:18:57 PDT 2010
On Tue, 19 Oct 2010 10:00:15 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> On Mon, 18 Oct 2010 17:39:44 -0700
> Greg Thelen <gthelen at google.com> wrote:
> > If the current process is in a non-root memcg, then
> > global_dirty_limits() will consider the memcg dirty limit.
> > This allows different cgroups to have distinct dirty limits
> > which trigger direct and background writeback at different
> > levels.
> > Signed-off-by: Andrea Righi <arighi at develer.com>
> > Signed-off-by: Greg Thelen <gthelen at google.com>
> Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com>
Why FREEPAGES in memcg is not counted as dirtyable ?
More information about the Containers