From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 20 May 2005 18:26:24 +0900 (JST) Message-Id: <20050520.182624.67793132.taka@valinux.co.jp> Subject: Re: [PATCH 0/6] CKRM: Memory controller for CKRM From: Hirokazu Takahashi In-Reply-To: <20050519003008.GC25076@chandralinux.beaverton.ibm.com> References: <20050519003008.GC25076@chandralinux.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: sekharan@us.ibm.com Cc: ckrm-tech@lists.sourceforge.net, linux-mm@kvack.org List-ID: Hi Chandra, > Here is the latest CKRM Memory controller patch against the patchset Gerrit > released on 05/05/05. (snip) > These are set of patches that provides the control of memory under the CKRM > framework(Details at http://ckrm.sf.net). I eagerly wait for your > feedback/comments/suggestions/concerns etc., > > To All, > > I am looking for improvement suggestions > - to not have a field in the page data structure for the mem > controller > - to make vmscan.c cleaner. I think it's very heavy to move all pages, which are mapped to removing regions, to new classes every time. It always happens when doing exec() or exit(), while munmap and closing file don't. Pages associating with libc.so or text of shells might move around the all classes. IMHO, it would be enough to just leave them as they are. These pages would be released a little later if no class touch them, or they might be accessed from another class to migrate another class, or they might reused in the same class. I feel it's not needed to move these pages in hurry. I prefer the implementation light. What do you think? BTW, the memory controller would be a good new to video streaming guys, I guess. Thanks, Hirokazu Takahashi. -- 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: aart@kvack.org