From: Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>
To: d@taht.net (Dave Täht)
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The wireless problem in a nutshell
Date: Tue, 08 Feb 2011 20:56:27 +0100 [thread overview]
Message-ID: <7ihbcecnbo.fsf@lanthane.pps.jussieu.fr> (raw)
In-Reply-To: <87oc6pf4bc.fsf@cruithne.co.teklibre.org> ("Dave =?iso-8859-1?Q?T=E4ht=22's?= message of "Sun, 06 Feb 2011 10:41:59 -0700")
> what you are also doing is dividing the TCP streams into two pieces -
> the wireless piece is VERY short - and congestion control then works
> correctly using existing techniques on the wired and unwired portions
> of the connection.
You've reinvented a useful technique, called "split-TCP". It's commonly
used by the "WAN accelerators" that you can buy in order to get Microsoft
protocols working across the Internet.
The downside of split-TCP, of course, is that it breaks e2e, and hence
fate sharing, i.e. it introduces a new point of failure and makes your
network more brittle. The challenge is to make TCP efficient without
the need for split-TCP, which requires differentiating between
congestion-induced loss and wireless loss.
--Juliusz
next prev parent reply other threads:[~2011-02-08 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 17:41 Dave Täht
2011-02-07 8:56 ` Luca Dionisi
2011-02-07 11:31 ` Dave Täht
2011-02-08 15:54 ` Justin McCann
2011-02-08 19:56 ` Juliusz Chroboczek [this message]
2011-02-08 21:54 ` Dave Täht
2011-02-10 18:39 ` Juliusz Chroboczek
2011-02-11 14:50 ` Dave Täht
2011-02-11 20:12 ` Stuart Cheshire
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ihbcecnbo.fsf@lanthane.pps.jussieu.fr \
--to=juliusz.chroboczek@pps.jussieu.fr \
--cc=bloat@lists.bufferbloat.net \
--cc=d@taht.net \
/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