From: Luca Dionisi <luca.dionisi@gmail.com>
To: "Dave Täht" <d@taht.net>,
"bufferbloat list" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The wireless problem in a nutshell
Date: Mon, 7 Feb 2011 09:56:43 +0100 [thread overview]
Message-ID: <AANLkTi=1mfBk+ntqG5OSq-uw6KgLfjTNJUKC2sfMvi8V@mail.gmail.com> (raw)
In-Reply-To: <87oc6pf4bc.fsf@cruithne.co.teklibre.org>
On Sun, Feb 6, 2011 at 6:41 PM, Dave Täht <d@taht.net> wrote:
> I personally regard the wireless packet loss burst problem as completely
> intractable for long TCP links without using proxies - or insane amounts
> of buffering.
Is this particular aspect going to be different once that nRED is complete?
I mean, if you were in a mesh network, primarily made of wireless
links, where the RTT becomes easily high, how could you make TCP links
to behave right?
--Luca
next prev parent reply other threads:[~2011-02-07 8:56 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 [this message]
2011-02-07 11:31 ` Dave Täht
2011-02-08 15:54 ` Justin McCann
2011-02-08 19:56 ` Juliusz Chroboczek
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='AANLkTi=1mfBk+ntqG5OSq-uw6KgLfjTNJUKC2sfMvi8V@mail.gmail.com' \
--to=luca.dionisi@gmail.com \
--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