[Devel] Re: [RFC] memory controller : backgorund reclaim and avoid excessive locking [5/5] lazy page_cgroup freeing

2008-02-17 Thread KAMEZAWA Hiroyuki
On Mon, 18 Feb 2008 10:58:40 +0900 (JST) [EMAIL PROTECTED] (YAMAMOTO Takashi) wrote: + /* +* For lazy freeing (not GC) +*/ + struct { + struct mem_cgroup_per_zone *mz; + int num; +#define GARBAGE_MAXSIZE(16) +

[Devel] Re: [RFC] memory controller : backgorund reclaim and avoid excessive locking [5/5] lazy page_cgroup freeing

2008-02-17 Thread YAMAMOTO Takashi
+ /* + * For lazy freeing (not GC) + */ + struct { + struct mem_cgroup_per_zone *mz; + int num; +#define GARBAGE_MAXSIZE (16) + struct page_cgroup *vec[GARBAGE_MAXSIZE]; + } garbage[NR_CPUS];

[Devel] Re: [RFC] memory controller : backgorund reclaim and avoid excessive locking [5/5] lazy page_cgroup freeing

2008-02-17 Thread Balbir Singh
KAMEZAWA Hiroyuki wrote: A big lock contetion of memory controller is mz-lru_lock. This is acquired when 1. add to lru 2. remove from lru 3. scan lru list It seems 1. and 3. are unavoidable. but 2. can be delayed. This patch make removing page_cgorup from lru-list be lazy and

[Devel] Re: [RFC] memory controller : backgorund reclaim and avoid excessive locking [5/5] lazy page_cgroup freeing

2008-02-17 Thread KAMEZAWA Hiroyuki
On Mon, 18 Feb 2008 10:05:16 +0530 Balbir Singh [EMAIL PROTECTED] wrote: Hi, KAMEZAWA-San, For this and the next patch, do you know if there is a performance improvement? Have we measured it. The complexity of the code seems to be high, want to make sure it is worth it. I'd like to make