Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754237AbbBKWEe (ORCPT ); Wed, 11 Feb 2015 17:04:34 -0500 Received: from resqmta-ch2-08v.sys.comcast.net ([69.252.207.40]:37705 "EHLO resqmta-ch2-08v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753283AbbBKWEd (ORCPT ); Wed, 11 Feb 2015 17:04:33 -0500 Date: Wed, 11 Feb 2015 16:04:31 -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: 886 Lines: 24 On Wed, 11 Feb 2015, David Rientjes wrote: > > > > > > 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. > > > > If you do dummy functions for all the allocators, then this should be as > simple as unconditionally defining kmem_cache_free_array() and doing > EXPORT_SYMBOL() here and then using your current implementation of > __kmem_cache_free_array() for mm/slab.c. That works if I put an EXPORT_SYMBOL in mm/slab_common.c and define the function in mm/slub.c? -- 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/