From: Joe Smith <codesoldier1@gmail.com>
To: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: SKB Reference Question
Date: Wed, 1 Nov 2017 10:27:49 -0700 [thread overview]
Message-ID: <CABGNecw9thLB4XOFdWRghj6E_uMrFroVko-Up6hodS75hmb4sg@mail.gmail.com> (raw)
How strictly are references on the SKB enforced. For example,
tcp_transmit_skb() clones the SKB and adds a TCP header. Can I assume
that in case of re-transmission the header added will be there and can
be reused instead of creating a new one from scratch. Some fields like
time stamp would need to be updated but they should be unmodified.
Regards,
--
JS
next reply other threads:[~2017-11-01 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 17:27 Joe Smith [this message]
2017-11-01 17:33 ` SKB Reference Question Eric Dumazet
2017-11-01 19:22 ` Joe Smith
2017-11-01 19:44 ` Eric Dumazet
2017-11-02 5:35 ` 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=CABGNecw9thLB4XOFdWRghj6E_uMrFroVko-Up6hodS75hmb4sg@mail.gmail.com \
--to=codesoldier1@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).