From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail190.messagelabs.com (mail190.messagelabs.com [216.82.249.51]) by kanga.kvack.org (Postfix) with ESMTP id E39356B009A for ; Wed, 20 Oct 2010 01:27:11 -0400 (EDT) Date: Wed, 20 Oct 2010 14:25:54 +0900 From: Daisuke Nishimura Subject: Re: [PATCH v3 11/11] memcg: check memcg dirty limits in page writeback Message-Id: <20101020142554.75c09286.nishimura@mxp.nes.nec.co.jp> In-Reply-To: <1287448784-25684-12-git-send-email-gthelen@google.com> References: <1287448784-25684-1-git-send-email-gthelen@google.com> <1287448784-25684-12-git-send-email-gthelen@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Greg Thelen Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, containers@lists.osdl.org, Andrea Righi , Balbir Singh , KAMEZAWA Hiroyuki , Minchan Kim , Ciju Rajan K , David Rientjes , Daisuke Nishimura List-ID: On Mon, 18 Oct 2010 17:39:44 -0700 Greg Thelen 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 > Signed-off-by: Greg Thelen Reviewed-by: Daisuke Nishimura -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org