[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1509565465.3828.47.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Wed, 01 Nov 2017 12:44:25 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Joe Smith <codesoldier1@...il.com>
Cc: netdev@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: SKB Reference Question
On Wed, 2017-11-01 at 12:22 -0700, Joe Smith wrote:
> On Wed, Nov 1, 2017 at 10:33 AM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> > On Wed, 2017-11-01 at 10:27 -0700, Joe Smith wrote:
> >> 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.
> >
> >
> > Not sure what you are trying to do, but this seems messy ;)
>
> As an example, consider reusing options that might be expensive to
> calculate. Assuming no coalescing.
>
> >
> > At rtx time, there is no guarantee that the master skb has not been
> > changed, so the content of TCP header might be wrong anyway.
>
> I would have thought that each layer below TCP would only add itÅ› own
> header and would not touch anything else. Is that not the guarantee
> that SKB references provideÅ›, or else the data could be changed.
>
> Can you give an example why the TCP header could change.
Before rtx, skbs can be split or coalesced.
Depending on ACK received from opposite peer, available cwnd budget,
pacing rate...
Also ECN can play a role.
Powered by blists - more mailing lists