From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lameter Subject: Re: [PATCH net-next] net: allocate skbs on local node Date: Wed, 13 Oct 2010 16:43:36 -0500 (CDT) Message-ID: References: <1286838210.30423.128.camel@edumazet-laptop> <1286839363.30423.130.camel@edumazet-laptop> <1286859925.30423.184.camel@edumazet-laptop> <20101011230322.f0f6dd47.akpm@linux-foundation.org> <1286866699.30423.234.camel@edumazet-laptop> <20101012002435.f51f2c0e.akpm@linux-foundation.org> <1286869793.2732.24.camel@edumazet-laptop> <20101012005856.994bea6d.akpm@linux-foundation.org> <4CB441CB.2000708@cs.helsinki.fi> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Pekka Enberg , Andrew Morton , Eric Dumazet , David Miller , netdev , Michael Chan , Eilon Greenstein , Christoph Hellwig , LKML , Nick Piggin To: David Rientjes Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, 13 Oct 2010, David Rientjes wrote: > > Basically have slab.c with the basic functions and then slab_queueing.c > > and slab_noqueue.c for SLAB/SLUB with the particulars of the allocation > > strategy? > > > > I was going to mention that as an idea, but I thought storing the metadata > for certain debugging features might differ from the two allocators so > substantially that it would be even more convoluted and difficult to > maintain? We could have some callbacks to store allocator specific metadata?