Messages in this thread | | | Date | Tue, 7 Jun 2011 16:46:16 +0900 | From | KAMEZAWA Hiroyuki <> | Subject | Re: [PATCH v8 09/12] memcg: create support routines for writeback |
| |
On Fri, 3 Jun 2011 09:12:15 -0700 Greg Thelen <gthelen@google.com> 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() determines if an inode is > contributing pages to an over-limit memcg. A new writeback_control > field determines if shared inodes should be written back. > > - 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. > > Signed-off-by: Greg Thelen <gthelen@google.com>
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
| |