From: Dave Taht <dave.taht@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Bufferbloat related censorship at Virgin Media
Date: Sun, 1 Mar 2015 16:25:31 -0800 [thread overview]
Message-ID: <CAA93jw7_WCoXPD=jAUT==jeNvhgLuJ1NtPaxK3pFnVq8aNb1GA@mail.gmail.com> (raw)
In-Reply-To: <20150302001706.GA33556@sesse.net>
On Sun, Mar 1, 2015 at 4:17 PM, Steinar H. Gunderson
<sgunderson@bigfoot.com> wrote:
> On Sun, Mar 01, 2015 at 04:01:02PM -0800, Dave Taht wrote:
>> http://snapon.lab.bufferbloat.net/~d/ieee802.11-sept-17-2014/11-14-1265-00-0wng-More-on-Bufferbloat.pdf
>
> I see “remove reorder buffers” and I'm scared; all the world is not TCP...
> (My ISP reorders packets a _lot_, and it messes up my multicast TV a _lot_.)
That is one of the concepts in there that I haven't explained very
well. Once we have multistation queueing working,
we will be able to switch to another station(s), while an aggregate
experiencing problems is retried for another station.
what happens now in many APs - is that all the packets get held up
until all packets arrive, thus inducing latency. This version,
of the ideas, gets the retransmit right while not blocking anything
else, nor (except in circumstances where aggregates for a given
station are being transmitted back to back, which is something we need
to be aware of and compensate for) does it cause re-ordering problems,
particularly if we are fq aware on the scheduling of each flow.
Secondly, you are describing multicast, and NOTHING on wifi is going
to fix ooo problems there - lost packets are just, lost packets.
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
prev parent reply other threads:[~2015-03-02 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 23:28 Dave Taht
[not found] ` <A665ECE3-FAFA-4624-B78B-1BCF10E94631@beckman.org>
2015-03-02 0:01 ` Dave Taht
2015-03-02 0:17 ` Steinar H. Gunderson
2015-03-02 0:25 ` Dave Taht [this message]
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='CAA93jw7_WCoXPD=jAUT==jeNvhgLuJ1NtPaxK3pFnVq8aNb1GA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=sgunderson@bigfoot.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