Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261770AbVC3GmK (ORCPT ); Wed, 30 Mar 2005 01:42:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261769AbVC3GmI (ORCPT ); Wed, 30 Mar 2005 01:42:08 -0500 Received: from zeus.kernel.org ([204.152.189.113]:20121 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id S261767AbVC3Glt (ORCPT ); Wed, 30 Mar 2005 01:41:49 -0500 Message-ID: <424A3FA0.9030403@colorfullife.com> Date: Wed, 30 Mar 2005 07:56:48 +0200 From: Manfred Spraul User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.7.6) Gecko/20050323 Fedora/1.7.6-1.3.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christoph Lameter CC: "Martin J. Bligh" , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, shai@scalex86.org Subject: Re: API changes to the slab allocator for NUMA memory allocation References: <20050315204110.6664771d.akpm@osdl.org> <42387C2E.4040106@colorfullife.com> <273220000.1110999247@[10.10.2.4]> <4238845E.5060304@colorfullife.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1249 Lines: 32 Christoph Lameter wrote: >The patch makes the following function calls available to allocate memory on >a specific node without changing the basic operation of the slab >allocator: > > kmem_cache_alloc_node(kmem_cache_t *cachep, unsigned int flags, int node); > kmalloc_node(size_t size, unsigned int flags, int node); > > > I intentionally didn't add a kmalloc_node() function: kmalloc is just a wrapper around kmem_find_general_cachep+kmem_cache_alloc. It exists only for efficiency. The _node functions are slow, thus a wrapper is IMHO not required. kmalloc_node(size,flags,node) is identical to kmem_cache_alloc(kmem_find_general_cachep(size,flags),flags,node). What about making kmem_find_general_cachep() public again and removing kmalloc_node()? And I don't know if it's a good idea to make kmalloc() a special case of kmalloc_node(): It adds one parameter to every kmalloc call and kmem_cache_alloc call, virtually everyone passes -1. Does it increase the .text size? -- Manfred - 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/