From: Rick Jones <rick.jones2@hp.com>
To: Josh Lehan <linux@krellan.com>
Cc: Yuchung Cheng <ycheng@google.com>,
netdev <netdev@vger.kernel.org>,
jiyengar@fandm.edu
Subject: Re: Skipping past TCP lost packet in userspace
Date: Wed, 01 Jun 2011 10:35:23 -0700 [thread overview]
Message-ID: <1306949723.8149.2202.camel@tardy> (raw)
In-Reply-To: <4DE5F3E3.2080609@krellan.com>
On Wed, 2011-06-01 at 01:10 -0700, Josh Lehan wrote:
> On 05/31/2011 10:23 AM, Yuchung Cheng wrote:
> > This paper may have a solution to your problem
> > "Minion—an All-Terrain Packet Packhorse to Jump-Start Stalled Internet
> > Transports"
> > http://csweb1.fandm.edu/jiyengar/lair/papers/minion-pfldnet2010.pdf
>
> Nice, thanks for pointing me to this. I appreciate the helpful answer,
> instead of just saying "use UDP" or "use SCTP". That's not the point.
>
> For better or for worse, TCP is realistically the only viable protocol
> for streaming to the largest possible audience these days, hence my
> question about adding this feature to the Linux TCP implementation.
Isn't that treating the symptoms of problems at layers 8 and 9 (*) with
kludges (perhaps hacks if one is feeling charitable) at the user
interface to layer 4? Just how many more little bits can we add to the
great pile before the aroma is overpowering? Or to abuse another
metaphor, is there really any camel's back left here?
And while Linux has had some slightly non-trivial, non-portable
enhancements to its interface to a TCP endpoint (TCP_CORK is something
that comes to mind) I don't think any of them have been anywhere nearly
as large a change to a fundamental semantic of a TCP connection as what
you propose.
rick jones
*
http://www.isc.org/store/logoware-clothing/isc-9-layer-osi-model-cotton-t-shirt
next prev parent reply other threads:[~2011-06-01 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 1:19 Skipping past TCP lost packet in userspace Josh Lehan
2011-05-31 3:30 ` Marcus D. Leech
2011-05-31 4:12 ` Josh Lehan
2011-05-31 4:05 ` Mikael Abrahamsson
2011-05-31 11:12 ` Neil Horman
2011-05-31 17:23 ` Yuchung Cheng
2011-06-01 8:10 ` Josh Lehan
2011-06-01 16:57 ` Bill Sommerfeld
2011-06-01 17:35 ` Rick Jones [this message]
2011-06-24 14:58 ` Janardhan Iyengar
2011-06-30 8:38 ` Josh Lehan
2011-06-30 14:36 ` Neil Horman
2011-07-01 8:39 ` Josh Lehan
2011-07-01 13:37 ` Neil Horman
2011-06-01 19:36 ` juice
2011-06-03 11:51 ` Ilpo Järvinen
2011-06-06 6:30 ` Josh Lehan
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=1306949723.8149.2202.camel@tardy \
--to=rick.jones2@hp.com \
--cc=jiyengar@fandm.edu \
--cc=linux@krellan.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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).