From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Tom Herbert" <therbert@google.com>,
"Maciej Żenczykowski" <maze@google.com>,
"Yuchung Cheng" <ycheng@google.com>
Subject: Re: [PATCH net-next] tcp: avoid expensive pskb_expand_head() calls
Date: Wed, 18 Apr 2012 21:18:27 +0200 [thread overview]
Message-ID: <1334776707.2472.316.camel@edumazet-glaptop> (raw)
In-Reply-To: <CADVnQy=BkhSBHyN2hyBy=_H64oM8sJvyZZfEjK1x7PYzoLv=5w@mail.gmail.com>
On Wed, 2012-04-18 at 14:40 -0400, Neal Cardwell wrote:
>
> > + prev_packets_acked = tcp_skb_pcount(skb);
>
> FWIW, I'd find old_pcount or prev_pcount a little easier to read than
> prev_packets_acked here (I see "oldpcount" is used in tcp_output
> in a similar context).
>
You're right, I'll change this.
> > TCP_SKB_CB(skb)->seq += len;
> > + TCP_SKB_CB(skb)->header.offset_ack = 0;
>
> If the caller decides to trim a prefix of the skb that does not extend
> to snd_una, then setting offset_ack to 0 here will cause us to forget
> that some prefix is ACKed when we should have remembered this.
> However, the API for the function invites the caller to chop off an
> arbitrary amount (and there's no comment to disuade the caller from
> trying this). This seems to risk bugs in the future.
>
> To attempt to make this API safer and simpler for future generations,
> what do you think about calculating the len inside tcp_trim_head(),
> something like:
>
> static int tcp_trim_head(struct sock *sk, struct sk_buff *skb)
> {
> u32 len = tp->snd_una - TCP_SKB_CB(skb)->seq;
> ...
>
> ...
> if (tcp_trim_head(sk, skb))
> ...
>
Very good point, I'll use this suggestion too in v2.
Thanks !
next prev parent reply other threads:[~2012-04-18 19:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 9:06 [BUG] ixgbe: something wrong with queue selection ? Eric Dumazet
2012-04-17 9:16 ` Jeff Kirsher
2012-04-17 16:01 ` Alexander Duyck
2012-04-17 16:38 ` John Fastabend
2012-04-17 17:07 ` Ben Hutchings
2012-04-17 16:46 ` Eric Dumazet
2012-04-17 21:38 ` TSO not 10G friendly if peer is close enough Eric Dumazet
2012-04-17 21:47 ` David Miller
2012-04-18 3:00 ` Eric Dumazet
2012-04-18 15:49 ` [PATCH net-next] tcp: avoid expensive pskb_expand_head() calls Eric Dumazet
[not found] ` <4F8EF317.10504@hp.com>
2012-04-18 17:16 ` Eric Dumazet
2012-04-18 17:30 ` Rick Jones
2012-04-18 17:40 ` Eric Dumazet
2012-04-18 18:40 ` Neal Cardwell
2012-04-18 19:18 ` Eric Dumazet [this message]
2012-04-18 19:51 ` [PATCH v2 " Eric Dumazet
2012-04-19 11:10 ` Ilpo Järvinen
2012-04-19 11:30 ` Eric Dumazet
2012-04-19 11:40 ` Eric Dumazet
2012-04-19 11:57 ` Ilpo Järvinen
2012-04-19 12:44 ` Eric Dumazet
2012-04-20 12:27 ` Ilpo Järvinen
2012-04-19 13:18 ` Eric Dumazet
2012-04-19 13:52 ` Eric Dumazet
2012-04-19 14:10 ` Eric Dumazet
2012-04-19 17:20 ` Rick Jones
2012-04-19 17:25 ` Eric Dumazet
2012-04-19 17:48 ` Rick Jones
2012-04-19 18:00 ` Eric Dumazet
2012-04-19 18:05 ` Rick Jones
2012-04-18 19:41 ` [PATCH " Vijay Subramanian
2012-04-18 19:49 ` Eric Dumazet
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=1334776707.2472.316.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=maze@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
--cc=ycheng@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox