From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with ESMTP id 1EE556B0185 for ; Wed, 17 Aug 2011 21:20:36 -0400 (EDT) Received: from m3.gw.fujitsu.co.jp (unknown [10.0.50.73]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id E29993EE0BB for ; Thu, 18 Aug 2011 10:20:32 +0900 (JST) Received: from smail (m3 [127.0.0.1]) by outgoing.m3.gw.fujitsu.co.jp (Postfix) with ESMTP id CBE0745DEB2 for ; Thu, 18 Aug 2011 10:20:32 +0900 (JST) Received: from s3.gw.fujitsu.co.jp (s3.gw.fujitsu.co.jp [10.0.50.93]) by m3.gw.fujitsu.co.jp (Postfix) with ESMTP id B6A9945DE9E for ; Thu, 18 Aug 2011 10:20:32 +0900 (JST) Received: from s3.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s3.gw.fujitsu.co.jp (Postfix) with ESMTP id A955D1DB8037 for ; Thu, 18 Aug 2011 10:20:32 +0900 (JST) Received: from ml13.s.css.fujitsu.com (ml13.s.css.fujitsu.com [10.240.81.133]) by s3.gw.fujitsu.co.jp (Postfix) with ESMTP id 72FC41DB803B for ; Thu, 18 Aug 2011 10:20:32 +0900 (JST) Date: Thu, 18 Aug 2011 10:13:04 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [PATCH v9 09/13] memcg: create support routines for writeback Message-Id: <20110818101304.fa662053.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <1313597705-6093-10-git-send-email-gthelen@google.com> References: <1313597705-6093-1-git-send-email-gthelen@google.com> <1313597705-6093-10-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 List-ID: To: Greg Thelen Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, containers@lists.osdl.org, linux-fsdevel@vger.kernel.org, Balbir Singh , Daisuke Nishimura , Minchan Kim , Johannes Weiner , Wu Fengguang , Dave Chinner , Vivek Goyal , Andrea Righi , Ciju Rajan K , David Rientjes On Wed, 17 Aug 2011 09:15:01 -0700 Greg Thelen wrote: > Introduce memcg routines to assist in per-memcg writeback: > > - mem_cgroups_over_bground_dirty_thresh() determines if any cgroups need > writeback because they are over their dirty memory threshold. > > - should_writeback_mem_cgroup_inode() will be called by writeback to > determine if a particular inode should be written back. The answer > depends on the writeback context (foreground, background, > try_to_free_pages, etc.). > > - mem_cgroup_writeback_done() is used periodically during writeback to > update memcg writeback data. > > These routines make use of a new over_bground_dirty_thresh bitmap that > indicates which mem_cgroup are over their respective dirty background > threshold. As this bitmap is indexed by css_id, the largest possible > css_id value is needed to create the bitmap. So move the definition of > CSS_ID_MAX from cgroup.c to cgroup.h. This allows users of css_id() to > know the largest possible css_id value. This knowledge can be used to > build such per-cgroup bitmaps. > > Make determine_dirtyable_memory() non-static because it is needed by > mem_cgroup_writeback_done(). > > Signed-off-by: Greg Thelen Acked-by: KAMEZAWA Hiroyuki -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org