From: Joe Smith
Date: Wed, 1 Nov 2017 10:27:49 -0700
> 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 n
On Wed, 2017-11-01 at 12:22 -0700, Joe Smith wrote:
> On Wed, Nov 1, 2017 at 10:33 AM, Eric Dumazet 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
On Wed, Nov 1, 2017 at 10:33 AM, Eric Dumazet 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 w
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
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
