From: Dmitry Kravkov <dkravkov@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jerry Chu <hkchu@google.com>, Tom Herbert <therbert@google.com>
Subject: Re: [PATCH net-next 5/6] ipip: add GSO/TSO support
Date: Sat, 19 Oct 2013 23:00:50 +0200 [thread overview]
Message-ID: <CAM8tLiN4M5RhFzp0VMU7mwqOTUiL+BGJ3vZ4X-zRjBAugbRzXA@mail.gmail.com> (raw)
In-Reply-To: <1382208178-22347-6-git-send-email-edumazet@google.com>
> diff --git a/net/ipv4/gre_offload.c b/net/ipv4/gre_offload.c
> index 55e6bfb..e5d4361 100644
> --- a/net/ipv4/gre_offload.c
> +++ b/net/ipv4/gre_offload.c
> @@ -39,7 +39,8 @@ static struct sk_buff *gre_gso_segment(struct sk_buff *skb,
> SKB_GSO_UDP |
> SKB_GSO_DODGY |
> SKB_GSO_TCP_ECN |
> - SKB_GSO_GRE)))
> + SKB_GSO_GRE |
> + SKB_GSO_IPIP)))
> goto out;
Why GRE needs this bit?
next prev parent reply other threads:[~2013-10-19 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 18:42 [PATCH net-next 0/6] net: Implement GSO/TSO support for IPIP Eric Dumazet
2013-10-19 18:42 ` [PATCH net-next 1/6] ipv4: gso: send_check() & segment() cleanups Eric Dumazet
2013-10-19 18:42 ` [PATCH net-next 2/6] net: generalize skb_segment() Eric Dumazet
2013-10-19 18:42 ` [PATCH net-next 3/6] ipv4: generalize gre_handle_offloads Eric Dumazet
2013-10-19 18:42 ` [PATCH net-next 4/6] ipv4: gso: make inet_gso_segment() stackable Eric Dumazet
2013-10-19 18:42 ` [PATCH net-next 5/6] ipip: add GSO/TSO support Eric Dumazet
2013-10-19 21:00 ` Dmitry Kravkov [this message]
2013-10-19 18:42 ` [PATCH net-next 6/6] bnx2x: add TSO support for IPIP Eric Dumazet
2013-10-19 18:59 ` [PATCH net-next 0/6] net: Implement GSO/TSO " Eric Dumazet
2013-10-19 23:37 ` 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=CAM8tLiN4M5RhFzp0VMU7mwqOTUiL+BGJ3vZ4X-zRjBAugbRzXA@mail.gmail.com \
--to=dkravkov@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkchu@google.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@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;
as well as URLs for NNTP newsgroup(s).