On Thu, Jul 24, 2008 at 10:56:08PM +1000, Nick Piggin wrote:
quoted text > > > OTOH, skb allocation uses kmalloc don't they? So you could still use
> > > SLOB ksize for that I guess.
On Thursday 24 July 2008 23:04, Herbert Xu wrote:
quoted text > > Yes I was referring to the data portion which is kmalloc'ed.
> > That is also why I'm interested in ksize because a priori we
> > don't know exactly how big it's going to be. However, we do
> > know that statistically 1500 will dominate.
> >
> > I'm not interested in ksize for kmem_cache at all. So in fact
> > we could have something simpler that's based on kmalloc's rounding
> > algorithm instead.
On Thu, 2008-07-24 at 23:13 +1000, Nick Piggin wrote:
quoted text > Yes you could definitely have a function that returns allocated
> bytes for a given kmalloc size. Should be about as fast or faster
> than extracting the size from the kaddr...
Yup, makes sense.
--
unsubscribe notice 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/
Messages in current thread:
Re: [regression] nf_iterate(), BUG: unable to handle kernel ... , Pekka Enberg , (Thu Jul 24, 9:32 am)