From: Rick Jones <rick.jones2@hp.com>
To: Andreas Petlund <apetlund@simula.no>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Arnd Hannemann" <hannemann@nets.rwth-aachen.de>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
shemminger@vyatta.com, "David Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/3] net: TCP thin linear timeouts
Date: Thu, 29 Oct 2009 10:01:57 -0700 [thread overview]
Message-ID: <4AE9CA85.9080409@hp.com> (raw)
In-Reply-To: <58396856-6D7E-4CE1-8D66-D1F11205B0D5@simula.no>
Just how thin can a thin stream be when a thin stream is found thin? (to the
cadence of "How much wood could a woodchuck chuck if a woodchuck could chuck wood?")
Does a stream get so thin that a user's send could not be split into four,
sub-MSS TCP segments?
rick jones
next prev parent reply other threads:[~2009-10-29 17:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 16:31 [PATCH 2/3] net: TCP thin linear timeouts Andreas Petlund
2009-10-27 16:56 ` Eric Dumazet
2009-10-28 12:58 ` Arnd Hannemann
2009-10-28 14:31 ` Ilpo Järvinen
2009-10-29 13:51 ` Andreas Petlund
2009-10-29 14:24 ` Eric Dumazet
2009-10-29 17:01 ` Rick Jones [this message]
[not found] ` <07CD1135-C68B-4264-8CD3-C4BC0400FDA2@simula.no>
2009-10-29 16:11 ` Arnd Hannemann
2009-10-28 3:20 ` William Allen Simpson
2009-10-29 13:50 ` Andreas Petlund
2009-10-28 14:18 ` Ilpo Järvinen
-- strict thread matches above, loose matches on Subject: below --
2009-10-29 15:14 apetlund
2009-10-29 15:19 apetlund
2009-10-29 15:43 apetlund
2009-10-29 15:50 ` Eric Dumazet
2009-10-29 20:52 ` Ilpo Järvinen
2009-10-29 16:54 apetlund
2009-10-30 10:48 apetlund
2009-10-30 17:33 ` Rick Jones
2009-10-30 18:11 ` William Allen Simpson
2009-11-05 13:37 ` Andreas Petlund
2009-10-30 15:27 apetlund
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=4AE9CA85.9080409@hp.com \
--to=rick.jones2@hp.com \
--cc=apetlund@simula.no \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannemann@nets.rwth-aachen.de \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).