From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tore Anderson <tore@fud.no>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] ipv6: dst_allfrag() not taken into account by TCP
Date: Wed, 18 Jan 2012 15:06:09 +0100 [thread overview]
Message-ID: <1326895569.2316.14.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <00f1ef555b452980aae95eb3028072f8@localhost>
Le mercredi 18 janvier 2012 à 13:42 +0100, Tore Anderson a écrit :
> * Eric Dumazet
>
> > Could you please test following patch ?
>
> Hi,
>
> It seems to work fine, now all the outgoing packets that includes a
> Fragmentation header all are "atomic" or "non-fragmented" fragments,
> i.e., that they both have Offset=0 and More Fragments=0.
>
> I'm uploaded a tcpdump showing the traffic with the patch here:
>
> https://bugzilla.kernel.org/attachment.cgi?id=72106
>
> Best regards,
Seems good, thanks !
Now I wonder if some RFC can allow us to send small frames without a
frag header, since this frag header forces us to perform tx checksum in
software.
I guess 576 should be safe ?
diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
index d97e071..14cb938 100644
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -153,7 +153,7 @@ static int ip6_finish_output2(struct sk_buff *skb)
static int ip6_finish_output(struct sk_buff *skb)
{
if ((skb->len > ip6_skb_dst_mtu(skb) && !skb_is_gso(skb)) ||
- dst_allfrag(skb_dst(skb)))
+ (skb->len > 576 && dst_allfrag(skb_dst(skb))))
return ip6_fragment(skb, ip6_finish_output2);
else
return ip6_finish_output2(skb);
next prev parent reply other threads:[~2012-01-18 14:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 16:28 [RFC] ipv6: dst_allfrag() not taken into account by TCP Eric Dumazet
2012-01-17 17:34 ` David Miller
2012-01-17 18:15 ` Eric Dumazet
2012-01-17 18:25 ` David Miller
2012-01-17 20:03 ` Tore Anderson
2012-01-17 20:25 ` Eric Dumazet
2012-01-18 12:42 ` Tore Anderson
2012-01-18 14:06 ` Eric Dumazet [this message]
2012-01-18 14:43 ` Tore Anderson
2012-01-18 14:59 ` Eric Dumazet
2012-01-18 15:14 ` Tore Anderson
2012-01-18 15:40 ` Eric Dumazet
2012-01-18 17:01 ` David Miller
2012-01-17 23:43 ` Bugzilla 42595 Eric Dumazet
2012-01-18 10:58 ` Eric Dumazet
2012-01-18 13:44 ` Eric Dumazet
2012-01-18 14:20 ` Tore Anderson
2012-01-18 14:42 ` Eric Dumazet
2012-01-18 15:42 ` Eric Dumazet
2012-01-18 19:26 ` Tore Anderson
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=1326895569.2316.14.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tore@fud.no \
/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