From: David Miller <davem@davemloft.net>
To: saku@ytti.fi
Cc: rick.jones2@hp.com, netdev@vger.kernel.org
Subject: Re: TCP and reordering
Date: Tue, 27 Nov 2012 21:06:11 -0500 (EST) [thread overview]
Message-ID: <20121127.210611.1127622873924794001.davem@davemloft.net> (raw)
In-Reply-To: <CAAeewD9MtEx4uF6ezbBj7Ci5OzX8VK7p=WQ2TB3PfjmznA4X0w@mail.gmail.com>
From: Saku Ytti <saku@ytti.fi>
Date: Tue, 27 Nov 2012 19:15:20 +0200
> TCP used to be friendly to reordering before fast retransmit
> optimization was implemented.
You're talking about 20 years ago, because that's when fast
retrasnmit was created.
It's not like this got added recently.
And the gains of fast retransmit far outweigh whatever strange
justification would give for reordering packets on purpose.
next prev parent reply other threads:[~2012-11-28 2:06 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 [this message]
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
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=20121127.210611.1127622873924794001.davem@davemloft.net \
--to=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).