Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761544AbXEPHCg (ORCPT ); Wed, 16 May 2007 03:02:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755407AbXEPHCa (ORCPT ); Wed, 16 May 2007 03:02:30 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:51160 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753569AbXEPHC3 (ORCPT ); Wed, 16 May 2007 03:02:29 -0400 Date: Wed, 16 May 2007 00:02:36 -0700 (PDT) Message-Id: <20070516.000236.71091606.davem@davemloft.net> To: Geert.Uytterhoeven@sonycom.com Cc: clameter@sgi.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linuxppc-dev@ozlabs.org Subject: Re: Slab allocators: Define common size limitations From: David Miller In-Reply-To: References: X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 729 Lines: 15 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/