netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gaofeng <gaofeng@cn.fujitsu.com>
To: christoph.paasch@uclouvain.be
Cc: netdev@vger.kernel.org
Subject: Re: pskb_copy() in tcp_transmit_skb()
Date: Tue, 13 Sep 2011 17:29:25 +0800	[thread overview]
Message-ID: <4E6F2275.2050902@cn.fujitsu.com> (raw)
In-Reply-To: <201109131221.37561.christoph.paasch@uclouvain.be>

  于 2011年09月13日 17:21, Christoph Paasch 写道:
> Hi,
>
> I'm trying to understand the reason for the possible call to pskb_copy() in
> tcp_transmit_skb().
> I don't find, where we may have a cloned skb entering tcp_transmit_skb().
>
> The original pskb_copy() came from tcp_retransmit_skb() (commit
> dfb4b9dceb35c567a595ae5e9d035cfda044a103).
> But from that point, the git-history does not show where the pskb_copy() is
> coming from.
>
>
> Does somebody has an idea, how a cloned skb can be passed to
> tcp_transmit_skb() and thus trigger this call to pskb_copy().
>
>
> Thanks for your help,
> Christoph
>
>
> --
> Christoph Paasch
> PhD Student
>
> IP Networking Lab --- http://inl.info.ucl.ac.be
> MultiPath TCP in the Linux Kernel --- http://inl.info.ucl.ac.be/mptcp
> Université Catholique de Louvain
>
> www.rollerbulls.be
> --
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
maybe nat,nat can change the tcp packet header

  reply	other threads:[~2011-09-13  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13  9:21 pskb_copy() in tcp_transmit_skb() Christoph Paasch
2011-09-13  9:29 ` Gaofeng [this message]
2011-09-13 10:55   ` Christoph Paasch
2011-09-13 12:00     ` Gao feng
2011-09-13 12:02     ` Eric Dumazet
2011-09-13 12:41       ` Christoph Paasch
2011-09-13 12:51         ` Eric Dumazet
2011-09-13 16:34       ` David Miller

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=4E6F2275.2050902@cn.fujitsu.com \
    --to=gaofeng@cn.fujitsu.com \
    --cc=christoph.paasch@uclouvain.be \
    --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).