From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (unknown [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id B65E5DDEFD for ; Wed, 16 May 2007 17:02:30 +1000 (EST) Date: Wed, 16 May 2007 00:02:36 -0700 (PDT) Message-Id: <20070516.000236.71091606.davem@davemloft.net> To: Geert.Uytterhoeven@sonycom.com Subject: Re: Slab allocators: Define common size limitations From: David Miller In-Reply-To: References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: linuxppc-dev@ozlabs.org, linux-mm@kvack.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, clameter@sgi.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Geert Uytterhoeven Date: Wed, 16 May 2007 08:58:39 +0200 (CEST) > 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? I'm allocating up to 1MB for per-process TLB hash tables on sparc64. But I can gracefully handle failures and it's just a performance tweak to use such large sized tables.