From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 11 Mar 2008 16:54:45 +0100 From: Andi Kleen Subject: Re: [PATCH] [6/13] Core maskable allocator Message-ID: <20080311155445.GB27593@one.firstfloor.org> References: <20080307090716.9D3E91B419C@basil.firstfloor.org> <26256.1205249693@vena.lwn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26256.1205249693@vena.lwn.net> Sender: owner-linux-mm@kvack.org Return-Path: To: Jonathan Corbet Cc: Andi Kleen , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On Tue, Mar 11, 2008 at 09:34:53AM -0600, Jonathan Corbet wrote: > Hi, Andi, > > As I dig through this patch, I find it mostly makes sense; seems like it > could be a good idea. Thanks. > > > +struct page * > > +alloc_pages_mask(gfp_t gfp, unsigned size, u64 mask) > > +{ > > + unsigned long max_pfn = mask >> PAGE_SHIFT; > > The "mask" parameter isn't really a mask - it's an upper bound on the Actually it's both. > address of the allocated memory. Might it be better to call it > "max_addr" or "limit" or "ceiling" or some such so callers understand mask is the standard term used by the PCI-DMA API for the same thing and since one of the main purposes of the mask allocator is to implement underlying support for that interface it seemed fitting to use the same convention. -Andi -- 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