Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754043AbbBKSro (ORCPT ); Wed, 11 Feb 2015 13:47:44 -0500 Received: from resqmta-ch2-02v.sys.comcast.net ([69.252.207.34]:55625 "EHLO resqmta-ch2-02v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752429AbbBKSrn (ORCPT ); Wed, 11 Feb 2015 13:47:43 -0500 Date: Wed, 11 Feb 2015 12:47:41 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: David Rientjes cc: akpm@linuxfoundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, penberg@kernel.org, iamjoonsoo@lge.com, Jesper Dangaard Brouer Subject: Re: [PATCH 1/3] Slab infrastructure for array operations In-Reply-To: Message-ID: References: <20150210194804.288708936@linux.com> <20150210194811.787556326@linux.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1657 Lines: 49 On Tue, 10 Feb 2015, David Rientjes wrote: > > +int kmem_cache_alloc_array(struct kmem_cache *s, > > + gfp_t flags, size_t nr, void **p) > > +{ > > + int i = 0; > > + > > +#ifdef _HAVE_SLAB_ALLOCATOR_ARRAY_OPERATIONS > > + /* ... > > + i += slab_array_alloc_from_local(s, nr - i, p + i); > > + > > +#endif > > This patch is referencing functions that don't exist and can do so since > it's not compiled, but I think this belongs in the next patch. I also > think that this particular implementation may be slub-specific so I would > have expected just a call to an allocator-defined > __kmem_cache_alloc_array() here with i = __kmem_cache_alloc_array(). The implementation is generic and can be used in the same way for SLAB. SLOB does not have these types of object though. > return 0 instead of using _HAVE_SLAB_ALLOCATOR_ARRAY_OPERATIONS at all. Ok that is a good idea. I'll just drop that macro and have all allocators provide dummy functions. > > +#ifndef _HAVE_SLAB_ALLOCATOR_ARRAY_OPERATIONS > > +void kmem_cache_free_array(struct kmem_cache *s, size_t nr, void **p) > > +{ > > + __kmem_cache_free_array(s, nr, p); > > +} > > +EXPORT_SYMBOL(kmem_cache_free_array); > > +#endif > > + > > Hmm, not sure why the allocator would be required to do the > EXPORT_SYMBOL() if it defines kmem_cache_free_array() itself. This Keeping the EXPORT with the definition is the custom as far as I could tell. -- 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/