On Fri, 20 Jan 2006 16:08:28 +0900 KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> > include/linux/gfp.h | 3 > > include/linux/mm.h | 49 ++ > > include/linux/mmzone.h | 118 ++++++ > > include/linux/swap.h | 2 > > mm/Kconfig | 6 > > mm/page_alloc.c | 845 > > +++++++++++++++++++++++++++++++++++++++++++++---- > > mm/shmem.c | 2 > > mm/vmscan.c | 75 +++- > > 8 files changed, 1020 insertions(+), 80 deletions(-) > Could you divide this *large* patch to several pieces ? Ok, I'll split the patch. > It looks you don't want to use functions based on zones, buddy-system, > lru-list etc.. > I think what you want is just a hierarchical memory allocator. > Why do you modify zone and make codes complicated ? > Can your memory allocater be implimented like mempool or hugetlb ? > They are not so invasive. mempool and hugetlb require their own shrinking code, don't they? I guess that we would need the routines like mm/vmscan.c if we are going to shrink user pages. Instead, I'd like to reuse the shrinking code in mm/vmscan.c. Thanks, -- KUROSAWA, Takahiro ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
