From: David Woodhouse <dwmw2@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: saku@ytti.fi, rick.jones2@hp.com, netdev@vger.kernel.org
Subject: Re: TCP and reordering
Date: Wed, 28 Nov 2012 07:59:26 +0000 [thread overview]
Message-ID: <1354089566.21562.20.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20121127.210611.1127622873924794001.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 2170 bytes --]
On Tue, 2012-11-27 at 21:06 -0500, David Miller wrote:
> And the gains of fast retransmit far outweigh whatever strange
> justification would give for reordering packets on purpose.
My 'strange justification' for reordering, albeit not entirely on
purpose, is that a single ADSL line at 8Mb/s down, 448Kb/s up is less
bandwidth than I had to my dorm room 16 years ago. So I bond two of
them, and naturally expect a certain amount of reordering.
I've never really done much analysis of this though, and it's never
seemed to be a problem. Then again, I don't think I get *much*
reordering. Big downloads tend to look fairly much like this:
07:36:02.272979 IP6 2001:770:15f::2.http > 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530: Flags [.], seq 67016473:67017881, ack 124, win 110, options [nop,nop,TS val 2564943119 ecr 1096912240], length 1408
07:36:02.273478 IP6 2001:770:15f::2.http > 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530: Flags [.], seq 67017881:67019289, ack 124, win 110, options [nop,nop,TS val 2564943119 ecr 1096912240], length 1408
07:36:02.273507 IP6 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530 > 2001:770:15f::2.http: Flags [.], ack 67019289, win 11198, options [nop,nop,TS val 1096912356 ecr 2564943119], length 0
07:36:02.274727 IP6 2001:770:15f::2.http > 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530: Flags [.], seq 67019289:67020697, ack 124, win 110, options [nop,nop,TS val 2564943119 ecr 1096912241], length 1408
07:36:02.275151 IP6 2001:770:15f::2.http > 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530: Flags [.], seq 67020697:67022105, ack 124, win 110, options [nop,nop,TS val 2564943119 ecr 1096912241], length 1408
07:36:02.275184 IP6 2001:8b0:10b:1:e6ce:8fff:fe1f:f2c0.52530 > 2001:770:15f::2.http: Flags [.], ack 67022105, win 11198, options [nop,nop,TS val 1096912358 ecr 2564943119], length 0
I suppose it might be worse if the lines weren't running at the same
speed, and if the packets weren't running over the same path through the
telco between the ISP's LNS (which alternates one packet per line) and
my local DSLAM.
Short of going through whole dumps and looking, is there a good way to
get statistics?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2012-11-28 7:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 9:32 TCP and reordering Saku Ytti
2012-11-27 17:05 ` Rick Jones
2012-11-27 17:15 ` Saku Ytti
2012-11-27 18:00 ` Rick Jones
2012-11-28 2:06 ` David Miller
2012-11-28 7:26 ` Saku Ytti
2012-11-28 8:35 ` Vijay Subramanian
2012-11-28 8:54 ` Saku Ytti
2012-11-28 18:24 ` Rick Jones
2012-11-28 18:33 ` Eric Dumazet
2012-11-28 18:52 ` Vijay Subramanian
2012-11-28 18:44 ` Saku Ytti
2012-11-28 7:59 ` David Woodhouse [this message]
2012-11-28 8:21 ` Christoph Paasch
2012-11-28 8:22 ` Vijay Subramanian
2012-11-28 9:08 ` David Woodhouse
2012-11-28 11:02 ` Eric Dumazet
2012-11-28 11:49 ` David Woodhouse
2012-11-28 12:26 ` Eric Dumazet
2012-11-28 12:39 ` David Woodhouse
2012-11-28 12:52 ` Eric Dumazet
2012-11-28 15:47 ` David Woodhouse
2012-11-28 16:09 ` Eric Dumazet
2012-11-28 16:21 ` David Woodhouse
2012-11-28 16:19 ` Benjamin LaHaise
2012-11-28 16:41 ` David Woodhouse
2012-11-28 17:08 ` Benjamin LaHaise
2012-11-28 17:16 ` Eric Dumazet
2012-11-28 18:01 ` David Woodhouse
2012-11-29 15:10 ` Noel Grandin
2012-12-02 1:30 ` David Woodhouse
2012-12-02 2:40 ` Eric Dumazet
2012-12-02 9:31 ` David Woodhouse
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=1354089566.21562.20.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=saku@ytti.fi \
/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).