Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1422772AbWA1BJA (ORCPT ); Fri, 27 Jan 2006 20:09:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1422777AbWA1BJA (ORCPT ); Fri, 27 Jan 2006 20:09:00 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:53899 "EHLO e31.co.us.ibm.com") by vger.kernel.org with ESMTP id S1422772AbWA1BI7 (ORCPT ); Fri, 27 Jan 2006 20:08:59 -0500 Message-ID: <43DAC427.70801@us.ibm.com> Date: Fri, 27 Jan 2006 17:08:55 -0800 From: Matthew Dobson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051011) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Benjamin LaHaise CC: linux-kernel@vger.kernel.org, sri@us.ibm.com, andrea@suse.de, pavel@suse.cz, linux-mm@kvack.org Subject: Re: [patch 3/9] mempool - Make mempools NUMA aware References: <20060125161321.647368000@localhost.localdomain> <1138233093.27293.1.camel@localhost.localdomain> <20060127002331.GH10409@kvack.org> <43D96AEC.4030200@us.ibm.com> <20060127032307.GI10409@kvack.org> In-Reply-To: <20060127032307.GI10409@kvack.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1515 Lines: 34 Benjamin LaHaise wrote: > On Thu, Jan 26, 2006 at 04:35:56PM -0800, Matthew Dobson wrote: > >>Ummm... ok? But with only a simple flag, how do you know *which* mempool >>you're trying to use? What if you want to use a mempool for a non-slab >>allocation? > > > Are there any? A quick poke around has only found a couple of places > that use kzalloc(), which is still quite effectively a slab allocation. > There seems to be just one page user, the dm-crypt driver, which could > be served by a reservation scheme. A couple. If Andrew is willing to pick up the mempool patches I posted an hour or so ago, there will be only 4 mempool users that aren't using a common mempool allocator. Regardless of whether that happens, there are only a few users that aren't slab based: 1) mm/highmem.c - page based allocator 2) drivers/scsi/scsi_transport_iscsi.c - calls alloc_skb(), which does eventually end up making a slab allocation 3) drivers/md/raid1.c & raid10.c - easily the biggest mempool_alloc functions in the kernel. Non-trivial. 4) drivers/md/dm-crypt.c - the driver you mentioned, also using a page allocator So we could possibly get away with a reservation scheme, but a couple users would be non-trivial to fixup. -Matt - 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/