From: Ben Greear <greearb@candelatech.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Make TCP work better with re-ordered frames?
Date: Wed, 18 May 2016 07:00:46 -0700 [thread overview]
Message-ID: <573C758E.9050008@candelatech.com> (raw)
We are investigating a system that has fairly poor TCP throughput
with the 3.17 and 4.0 kernels, but evidently it worked pretty well
with 3.14 (I should be able to verify 3.14 later today).
One thing I notice is that a UDP download test shows lots of reordered
frames, so I am thinking maybe TCP is running slow because of this.
(We see about 800Mbps UDP download, but only 500Mbps TCP, even when
using 100 concurrent TCP streams.)
Is there some way to tune the TCP stack to better handle reordered frames?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2016-05-18 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 14:00 Ben Greear [this message]
2016-05-18 14:29 ` Make TCP work better with re-ordered frames? Eric Dumazet
2016-05-18 15:07 ` Ben Greear
2016-05-18 15:25 ` Eric Dumazet
2016-05-18 15:46 ` Ben Greear
2016-05-18 16:02 ` Eric Dumazet
2016-05-18 18:17 ` Yuchung Cheng
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=573C758E.9050008@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/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).