On Friday 10 October 2008 18:21, KAMEZAWA Hiroyuki wrote: > On Thu, 9 Oct 2008 16:41:03 +0200 > > Nick Piggin <npiggin@xxxxxxx> wrote: > > Hi, > > > > Just got bored of looking at other things, and started coding up the > > first step to remove writepage from vmscan. > > Can I make a question ? Is this "vmscan" here means > > - direct memory reclaim triggered by memory allocation failure > (alloc_pages()) and not > - kswapd > - memory resource controller hits its limit > > or including all memory reclaim path ? Anywhere that we writeout from LRUs (as opposed to from the inode). That probably includes all of the above. Actually, probably my first patch is not so critical. We can probably start by just special casing writepage for the swapout path, and then the writepage for filesystems becomes a slowpath which can do the extra locking and refcounting... -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
