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

quoted text
> 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@develer.com>
> Signed-off-by: Greg Thelen <gthelen@google.com>

Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@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.


--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/