From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 5 Jan 2006 09:47:26 +0000 Subject: Re: [Patch] New zone ZONE_EASY_RECLAIM take 4. (disable gfp_easy_reclaim bit)[5/8] Message-ID: <20060105094726.GA14735@skynet.ie> References: <20051220173013.1B10.Y-GOTO@jp.fujitsu.com> <43BAEDDD.8080805@austin.ibm.com> <20060105144247.491D.Y-GOTO@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20060105144247.491D.Y-GOTO@jp.fujitsu.com> From: mel@csn.ul.ie (Mel Gorman) Sender: owner-linux-mm@kvack.org Return-Path: To: Yasunori Goto Cc: jschopp@austin.ibm.com, Linux Kernel ML , linux-mm , Linux Hotplug Memory Support List-ID: On (05/01/06 14:43), Yasunori Goto didst pronounce: > > > > > =================================================================== > > > --- zone_reclaim.orig/fs/pipe.c 2005-12-16 18:36:20.000000000 +0900 > > > +++ zone_reclaim/fs/pipe.c 2005-12-16 19:15:35.000000000 +0900 > > > @@ -284,7 +284,7 @@ pipe_writev(struct file *filp, const str > > > int error; > > > > > > if (!page) { > > > - page = alloc_page(GFP_HIGHUSER); > > > + page = alloc_page(GFP_HIGHUSER & ~__GFP_EASY_RECLAIM); > > > if (unlikely(!page)) { > > > ret = ret ? : -ENOMEM; > > > break; > > > > That is a bit hard to understand. How about a new GFP_HIGHUSER_HARD or > > somesuch define back in patch 1, then use it here? > > It looks better. Thanks for your idea. > There are other places where GFP_HIGHUSER is used for pages that are not easily reclaimed. It is easier clearer to add __GFP_EASY_RECLAIM at the places you know pages are easily reclaimed rather than removing __GFP_EASY_RECLAIM from awkward places. -- Mel Gorman Part-time Phd Student University of Limerick IBM Dublin Software Lab -- 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