All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: David Miller <davem@davemloft.net>
Cc: eric.dumazet@gmail.com, Ian.Campbell@citrix.com,
	netdev@vger.kernel.org, xen-devel@lists.xensource.com,
	rusty@rustcorp.com.au
Subject: Re: SKB paged fragment lifecycle on receive
Date: Fri, 24 Jun 2011 13:11:59 -0700	[thread overview]
Message-ID: <4E04EF8F.6070900@goop.org> (raw)
In-Reply-To: <20110624.124624.1329947216240823992.davem@davemloft.net>

On 06/24/2011 12:46 PM, David Miller wrote:
> Pages get transferred between different SKBs all the time.
>
> For example, GRO makes extensive use of this technique.
> See net/core/skbuff.c:skb_gro_receive().
>
> It is just one example.

I see, and the new skb doesn't get a destructor copied from the
original, so there'd be no second callback.

Are the pages still attached to the first skb, or are they transferred
completely?

Thanks,
    J



  reply	other threads:[~2011-06-24 20:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 15:43 SKB paged fragment lifecycle on receive Ian Campbell
2011-06-24 15:43 ` Ian Campbell
2011-06-24 17:29 ` Jeremy Fitzhardinge
2011-06-24 17:56   ` Eric Dumazet
2011-06-24 18:21     ` Jeremy Fitzhardinge
2011-06-24 19:46       ` David Miller
2011-06-24 20:11         ` Jeremy Fitzhardinge [this message]
2011-06-24 20:27           ` David Miller
2011-06-25 11:58           ` Ian Campbell
2011-06-27 20:51             ` Jeremy Fitzhardinge
2011-06-28 10:25               ` Ian Campbell
2011-06-27 14:42     ` Ian Campbell
2011-06-27 22:49       ` David Miller
2011-06-28 10:24         ` Ian Campbell
2011-06-24 22:44   ` Ian Campbell
2011-06-24 22:48     ` Jeremy Fitzhardinge
2011-06-26 10:25 ` Michael S. Tsirkin
2011-06-27  9:41   ` Ian Campbell
2011-06-27 10:21     ` Michael S. Tsirkin
2011-06-27 10:54       ` Ian Campbell
2011-06-27 11:19         ` Michael S. Tsirkin

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=4E04EF8F.6070900@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.