netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Eric Barton" <eeb@bartonsoftware.com>
To: "'Eric Dumazet'" <dada1@cosmosbay.com>
Cc: "'David Miller'" <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: RE: PATCH zero-copy send completion callback
Date: Tue, 17 Oct 2006 13:23:10 +0100	[thread overview]
Message-ID: <020d01c6f1e7$029beb70$0281a8c0@ebpc> (raw)
In-Reply-To: <200610171101.38690.dada1@cosmosbay.com>

> > 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: eeb@bartonsoftware.com|
---------------------------------------------------



  reply	other threads:[~2006-10-17 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061016.135222.78711520.davem@davemloft.net>
2006-10-17  0:53 ` PATCH zero-copy send completion callback Eric Barton
2006-10-17  9:01   ` Eric Dumazet
2006-10-17 12:23     ` Eric Barton [this message]
2006-10-17 21:45       ` David Miller
2006-10-17 11:19   ` Evgeniy Polyakov
2006-10-17 12:50 Eric Barton
2006-10-17 13:13 ` Evgeniy Polyakov
     [not found] <20061017094643.GA28926@infradead.org>
2006-10-17 12:27 ` Eric Barton
  -- strict thread matches above, loose matches on Subject: below --
2006-10-16 18:21 Eric Barton
2006-10-16 17:25 Eric Barton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='020d01c6f1e7$029beb70$0281a8c0@ebpc' \
    --to=eeb@bartonsoftware.com \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).