[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1178302904.2767.6.camel@lappy>
Date: Fri, 04 May 2007 20:21:44 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Christoph Lameter <clameter@....com>
Cc: 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>,
Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [PATCH 08/40] mm: kmem_cache_objsize
On Fri, 2007-05-04 at 11:04 -0700, Christoph Lameter wrote:
> On Fri, 4 May 2007, Peter Zijlstra wrote:
>
> > > I could add a function that tells you how many object you could allocate
> > > from a slab without the page allocator becoming involved? It would count
> > > the object slots available on the partial slabs.
> >
> > I need to know how many pages to reserve to allocate a given number of
> > items from a given slab; assuming the partial slabs are empty. That is,
> > I need a worst case upper bound.
>
> Ok so you really need the number of objects per page? If you know the
> number of objects then you can calculate the pages needed which would be
> the maximum memory needed?
Yes, that would work.
-
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