From: Eric Dumazet <eric.dumazet@gmail.com>
To: Pekka Riikonen <priikone@iki.fi>
Cc: "Simon Horman" <horms@verge.net.au>,
dev@openvswitch.org, netdev@vger.kernel.org,
"Jesse Gross" <jesse@nicira.com>,
"Pravin B Shelar" <pshelar@nicira.com>,
jarno.rajahalme@nsn.com, "Maciej Żenczykowski" <maze@google.com>
Subject: Re: [PATCH next-next v4 1/2] net: Use 16bits for inner_*_headers fields of struct skbuff
Date: Wed, 22 May 2013 04:32:06 -0700 [thread overview]
Message-ID: <1369222326.3301.301.camel@edumazet-glaptop> (raw)
In-Reply-To: <alpine.GSO.2.00.1305220923130.11532@git.silcnet.org>
On Wed, 2013-05-22 at 09:25 +0200, Pekka Riikonen wrote:
> On Wed, 22 May 2013, Simon Horman wrote:
>
> > include/linux/skbuff.h | 63 +++++++-------------------------------------------
> > 1 file changed, 8 insertions(+), 55 deletions(-)
> >
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> > index 2e0ced1..3791615 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -509,9 +509,9 @@ struct sk_buff {
> > __u32 reserved_tailroom;
> > };
> >
> > - sk_buff_data_t inner_transport_header;
> > - sk_buff_data_t inner_network_header;
> > - sk_buff_data_t inner_mac_header;
> > + __u16 inner_transport_header;
> > + __u16 inner_network_header;
> > + __u16 inner_mac_header;
> > sk_buff_data_t transport_header;
> > sk_buff_data_t network_header;
> > sk_buff_data_t mac_header;
> >
> Why not take one more step and use 16-bit fields for the other header
> fields too: transport_header, network_header and mac_header?
Thats more risky [1], but definitely worth doing
[1]
commit 50bceae9bd3569d56744882f3012734d48a1d413
Author: Thomas Graf <tgraf@suug.ch>
Date: Thu Apr 11 10:57:18 2013 +0000
tcp: Reallocate headroom if it would overflow csum_start
If a TCP retransmission gets partially ACKed and collapsed multiple
times it is possible for the headroom to grow beyond 64K which will
overflow the 16bit skb->csum_start which is based on the start of
the headroom. It has been observed rarely in the wild with IPoIB due
to the 64K MTU.
Verify if the acking and collapsing resulted in a headroom exceeding
what csum_start can cover and reallocate the headroom if so.
A big thank you to Jim Foraker <foraker1@llnl.gov> and the team at
LLNL for helping out with the investigation and testing.
Reported-by: Jim Foraker <foraker1@llnl.gov>
Signed-off-by: Thomas Graf <tgraf@suug.ch>
Acked-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2013-05-22 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 6:57 [PATCH next-next v4 0/2] MPLS: Add limited GSO support Simon Horman
2013-05-22 6:57 ` [PATCH next-next v4 1/2] net: Use 16bits for inner_*_headers fields of struct skbuff Simon Horman
2013-05-22 7:25 ` Pekka Riikonen
2013-05-22 11:32 ` Eric Dumazet [this message]
2013-05-24 1:38 ` David Miller
2013-05-22 6:57 ` [PATCH next-next v4 2/2] MPLS: Add limited GSO support Simon Horman
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=1369222326.3301.301.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=dev@openvswitch.org \
--cc=horms@verge.net.au \
--cc=jarno.rajahalme@nsn.com \
--cc=jesse@nicira.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=priikone@iki.fi \
--cc=pshelar@nicira.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