From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with ESMTP id 03C8F6B01EF for ; Fri, 16 Apr 2010 19:56:36 -0400 (EDT) Date: Sat, 17 Apr 2010 01:56:18 +0200 From: Johannes Weiner Subject: Re: [PATCH] mm: disallow direct reclaim page writeback Message-ID: <20100416235618.GL20640@cmpxchg.org> References: <20100414085132.GJ25756@csn.ul.ie> <20100415023704.GC20640@cmpxchg.org> <20100415114043.D162.A69D9226@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100415114043.D162.A69D9226@jp.fujitsu.com> Sender: owner-linux-mm@kvack.org To: KOSAKI Motohiro Cc: Mel Gorman , Dave Chinner , Chris Mason , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org List-ID: On Thu, Apr 15, 2010 at 11:43:48AM +0900, KOSAKI Motohiro wrote: > > I already have some patches to remove trivial parts of struct scan_control, > > namely may_unmap, may_swap, all_unreclaimable and isolate_pages. The rest > > needs a deeper look. > > Seems interesting. but scan_control diet is not so effective. How much > bytes can we diet by it? Not much, it cuts 16 bytes on x86 32 bit. The bigger gain is the code clarification it comes with. There is too much state to keep track of in reclaim. -- 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: email@kvack.org