From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 16 May 2007 10:04:05 +0100 (IST) From: Mel Gorman Subject: Re: [PATCH 6/8] Add __GFP_TEMPORARY to identify allocations that are short-lived In-Reply-To: Message-ID: References: <20070515150311.16348.56826.sendpatchset@skynet.skynet.ie> <20070515150512.16348.58421.sendpatchset@skynet.skynet.ie> <20070516093633.c8571b62.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: KAMEZAWA Hiroyuki , linux-mm@kvack.org List-ID: On Tue, 15 May 2007, Christoph Lameter wrote: > On Wed, 16 May 2007, KAMEZAWA Hiroyuki wrote: > >> What kind of objects should be considered to be TEMPORARY (short-lived) ? >> It seems hard-to-use if no documentation. >> Could you add clear explanation in header file ? >> >> In my understanding, following case is typical. >> >> == >> foo() { >> alloc(); >> do some work >> free(); >> } >> == >> >> Other cases ? > > GFP_TEMPORARY means that the memory will be freed in a short time without > further kernel intervention. I.e. there is no reclaim pass, user > intervention or other cleanup needed. I think network slabs also fit that > description. > Exactly. Hint taken though. Better documentation of the flags is on the TODO list. -- Mel Gorman Part-time Phd Student Linux Technology Center 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