From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vervifontaine.sonycom.com (unknown [80.88.33.193]) by ozlabs.org (Postfix) with ESMTP id 8E42DDDE08 for ; Thu, 17 May 2007 18:45:07 +1000 (EST) Date: Thu, 17 May 2007 10:45:00 +0200 (CEST) From: Geert Uytterhoeven Sender: geert@sonytel.be To: Arnd Bergmann Subject: Re: Slab allocators: Define common size limitations In-Reply-To: <200705162342.08601.arnd@arndb.de> Message-ID: References: <200705162342.08601.arnd@arndb.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org, Andrew Morton , Christoph Lameter , Linux Kernel Development , linux-mm@kvack.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 16 May 2007, Arnd Bergmann wrote: > On Wednesday 16 May 2007, Geert Uytterhoeven wrote: > > What are the changes a large allocation will actually succeed? > > Is there an alignment rule for large allocations? > > > > E.g. for one of the PS3 drivers I need a physically contiguous 256 KiB-aligned > > block of 256 KiB. Currently I'm using __alloc_bootmem() for that, but maybe > > kmalloc() becomes a suitable alternative now? > > kmalloc is limited to 128KiB on most architectures. Normally there is no > need to use it anyway, just use __get_free_pages(). It will generally > succeed at early boot time, but not after the system has been running > for some time. Exactly my understanding. And __get_free_pages() returns PAGE_SIZE-aligned memory. So I'll keep the current code. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- Sony Network and Software Technology Center Europe (NSCE) Geert.Uytterhoeven@sonycom.com ------- The Corporate Village, Da Vincilaan 7-D1 Voice +32-2-7008453 Fax +32-2-7008622 ---------------- B-1935 Zaventem, Belgium