From: Eric Dumazet <eric.dumazet@gmail.com>
To: Pravin B Shelar <pshelar@nicira.com>
Cc: netdev@vger.kernel.org, edumazet@google.com, jesse@nicira.com,
bhutchings@solarflare.com, mirqus@gmail.com
Subject: Re: [PATCH net-next 3/3] GRE: Add TCP segmentation offload for GRE
Date: Thu, 14 Feb 2013 17:39:49 -0800 [thread overview]
Message-ID: <1360892389.6884.74.camel@edumazet-glaptop> (raw)
In-Reply-To: <1360871101-2086-1-git-send-email-pshelar@nicira.com>
On Thu, 2013-02-14 at 11:45 -0800, Pravin B Shelar wrote:
> Following patch adds GRE protocol offload handler so that
> skb_gso_segment() can segment GRE packets.
> SKB GSO CB is added to keep track of total header length so that
> skb_segment can push entire header. e.g. in case of GRE, skb_segment
> need to push inner and outer headers to every segment.
> New NETIF_F_GRE_GSO feature is added for devices which support HW
> GRE TSO offload. Currently none of devices support it therefore GRE GSO
> always fall backs to software GSO.
>
> Signed-off-by: Pravin B Shelar <pshelar@nicira.com>
> ---
> Fixed according to comments from Jesse and Eric.
> v2-v3:
> - Use device features to segment inner packet.
> - Moved skb_mac_gso_segment to separate patch.
> - simplified gre_gso_segment().
> - Added NETIF_F_GRE_GSO feature.
>
> v1-v2:
> - Factored a MAC layer handler out of skb_gso_segment().
> - Eliminated copy operation from gre_gso_segment().
> - Refresh header pointer after pskb_may_pull().
> ---
Seems very good to me, thanks !
The only thing that puzzles me is the ip_select_ident() in
ipgre_tunnel_xmit()
Do we care of the IP identifiers being 0, 1, 2, 3, ... on the outer
headers ?
Without TSO, we are using 0 IP identifiers (DF being set)
Also if we can't unclone the skb in handle_offloads(), we should
increment tx_dropped or tx_errors.
next prev parent reply other threads:[~2013-02-15 1:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 19:45 [PATCH net-next 3/3] GRE: Add TCP segmentation offload for GRE Pravin B Shelar
2013-02-15 1:39 ` Eric Dumazet [this message]
2013-02-15 3:19 ` Pravin Shelar
2013-02-15 2:35 ` Michał Mirosław
2013-02-15 3:31 ` Pravin Shelar
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=1360892389.6884.74.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=edumazet@google.com \
--cc=jesse@nicira.com \
--cc=mirqus@gmail.com \
--cc=netdev@vger.kernel.org \
--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