netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: hkchu@google.com, jesse@nicira.com, tom@herbertland.com,
	netdev@vger.kernel.org, kernel-team@fb.com, linux@stwm.de,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH net-next] ipv6: gro: support sit protocol
Date: Wed, 21 Oct 2015 19:37:02 -0700 (PDT)	[thread overview]
Message-ID: <20151021.193702.1623864743998748289.davem@davemloft.net> (raw)
In-Reply-To: <1445312417.30896.64.camel@edumazet-glaptop2.roam.corp.google.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Mon, 19 Oct 2015 20:40:17 -0700

> From: Eric Dumazet <edumazet@google.com>
> 
> Tom Herbert added SIT support to GRO with commit
> 19424e052fb4 ("sit: Add gro callbacks to sit_offload"),
> later reverted by Herbert Xu.
> 
> The problem came because Tom patch was building GRO
> packets without proper meta data : If packets were locally
> delivered, we would not care.
> 
> But if packets needed to be forwarded, GSO engine was not
> able to segment individual segments.
> 
> With the following patch, we correctly set skb->encapsulation
> and inner network header. We also update gso_type.
> 
> Tested:
 ...
> Checked on server traffic copied on dummy0 and verify segments were
> properly rebuilt, with proper IP headers, TCP checksums...
> 
> tcpdump on eth0 shows proper GRO aggregation takes place.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Applied.

  parent reply	other threads:[~2015-10-22  2:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 17:11 [PATCH v2 net-next 0/4] gro: Fixes for tunnels and GRO Tom Herbert
2015-08-03 17:11 ` [PATCH v2 net-next 1/4] gro: Fix remcsum offload to deal with frags in GRO Tom Herbert
2015-08-03 17:11 ` [PATCH v2 net-next 2/4] vxlan: GRO support at tunnel layer Tom Herbert
2015-08-03 17:11 ` [PATCH v2 net-next 3/4] ipv6: Add gro functions to sit_offloads Tom Herbert
2015-08-07  0:15   ` Jesse Gross
2015-10-16 15:23     ` Eric Dumazet
2015-10-20  2:04       ` Eric Dumazet
2015-10-20  3:40         ` [PATCH net-next] ipv6: gro: support sit protocol Eric Dumazet
2015-10-20  3:51           ` Tom Herbert
2015-10-22  2:37           ` David Miller [this message]
2015-11-03 12:57           ` Wolfgang Walter
2015-11-03 13:07             ` Eric Dumazet
2015-11-03 21:14               ` Tom Herbert
2015-11-04 12:19               ` Wolfgang Walter
2015-11-04 12:40                 ` Eric Dumazet
2015-11-04 14:09                   ` Wolfgang Walter
2015-11-04 15:13                     ` Eric Dumazet
2015-11-04 17:05                       ` Wolfgang Walter
2015-10-20  9:21       ` [PATCH v2 net-next 3/4] ipv6: Add gro functions to sit_offloads Wolfgang Walter
2015-08-03 17:11 ` [PATCH v2 net-next 4/4] fou: Do WARN_ON_ONCE in gue_gro_receive for bad proto callbacks Tom Herbert
2015-08-07  1:55 ` [PATCH v2 net-next 0/4] gro: Fixes for tunnels and GRO 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=20151021.193702.1623864743998748289.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hkchu@google.com \
    --cc=jesse@nicira.com \
    --cc=kernel-team@fb.com \
    --cc=linux@stwm.de \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).