[PATCH v4 11/11] memcg: check memcg dirty limits in page writeback

KAMEZAWA Hiroyuki kamezawa.hiroyu at jp.fujitsu.com
Fri Oct 29 00:48:35 PDT 2010


On Fri, 29 Oct 2010 00:09:14 -0700
Greg Thelen <gthelen at google.com> wrote:

> If the current process is in a non-root memcg, then
> balance_dirty_pages() will consider the memcg dirty limits
> as well as the system-wide limits.  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>

Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com>

Ideally, I think some comments in the code for "why we need double-check system's
dirty limit and memcg's dirty limit" will be appreciated.




More information about the Containers mailing list