> > Also, (please correct me if I'm wrong) I didn't
> > think this would push the allocation over to the next entry in
> > 'malloc_sizes'.
>
> Well, skbuff heads are allocated from dedicated kmem_cache
> (skbuff_fclone_cache & skbuff_head_cache), and these caches are not
> constrained by the sizes available in malloc_sizes. Their
> size are a multiple
> of L1 CACHE size, which is 64 bytes for most common machines.
Indeed, struct skbuff is so allocated. But I added the callback
pointers to struct skb_shared_info where the page pointers are stored,
and this struct is allocated along with the packet header using kmalloc.
> Even if your two pointers addition (16 bytes on x86_64)
> doesnt cross a 64bytes
> line (I didn't checked), they are going to be set to NULL
> each time a skbuff
> is allocated , and checked against NULL each time a skbuff is
> destroyed.
Indeed. Do you think that's significant?
Cheers,
Eric
---------------------------------------------------
|Eric Barton Barton Software |
|9 York Gardens Tel: +44 (117) 330 1575 |
|Clifton Mobile: +44 (7909) 680 356 |
|Bristol BS8 4LL Fax: call first |
|United Kingdom E-Mail: [EMAIL PROTECTED]|
---------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
