From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <463B7F63.8070508@cs.helsinki.fi> Date: Fri, 04 May 2007 21:45:55 +0300 From: Pekka Enberg MIME-Version: 1.0 Subject: Re: [PATCH 08/40] mm: kmem_cache_objsize References: <20070504102651.923946304@chello.nl> <20070504103157.215424767@chello.nl> <1178301545.24217.56.camel@twins> <1178302904.2767.6.camel@lappy> <1178303538.2767.9.camel@lappy> In-Reply-To: <1178303538.2767.9.camel@lappy> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Peter Zijlstra Cc: Christoph Lameter , linux-kernel@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, Trond Myklebust , Thomas Graf , David Miller , James Bottomley , Mike Christie , Andrew Morton , Daniel Phillips List-ID: On Fri, 2007-05-04 at 11:30 -0700, Christoph Lameter wrote: > > Hmmm... Maybe lets have > > > > unsigned kmem_estimate_pages(struct kmem_cache *slab_cache, int objects) > > > > which would calculate the worst case memory scenario for allocation the > > number of indicated objects? On Fri, 4 May 2007, Peter Zijlstra wrote: > Perfectly fine with me, Pekka, any objections? Again, slab has no way of actually estimating how many pages you need for a given number of objects. So we end up calculating some upper bound which doesn't belong in mm/slab.c. I am perfectly okay with: (1) kmem_nr_bytes_per_object which is what Peter has now or alternatively, (2) kmem_nr_objects_per_page which I think Christoph suggested Both of them, the slab knows the answer, and doesn't need to guess. It's up to the caller to figure out what the acceptable upper bound is. Pekka -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org