[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <463B7E5C.8030201@cs.helsinki.fi>
Date: Fri, 04 May 2007 21:41:32 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Christoph Lameter <clameter@....com>
CC: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
netdev@...r.kernel.org,
Trond Myklebust <trond.myklebust@....uio.no>,
Thomas Graf <tgraf@...g.ch>,
David Miller <davem@...emloft.net>,
James Bottomley <James.Bottomley@...elEye.com>,
Mike Christie <michaelc@...wisc.edu>,
Andrew Morton <akpm@...ux-foundation.org>,
Daniel Phillips <phillips@...gle.com>
Subject: Re: [PATCH 08/40] mm: kmem_cache_objsize
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?
IIRC this looks more or less what Peter had initially. I don't like the
API because there's no way for slab (perhaps this is different for slub)
how many pages you really need due to per-node and per-cpu caches, etc.
It's better that the slab tells you what it actually knows and lets the
callers figure out what a worst-case upper bound is.
Pekka
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists