From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] bufferbloat at high edge rates
Date: Mon, 14 Nov 2016 11:02:08 -0800 [thread overview]
Message-ID: <CAA93jw78qX2Eze-8FKBO7++hnd_iPCWBQ3N006J+qbZzMhbbhw@mail.gmail.com> (raw)
I do keep hoping it's really the browsers misbehaving.
http://www.dslreports.com/speedtest/6054627
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-11-14 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 19:02 Dave Taht [this message]
2016-11-14 20:06 ` Kathleen Nichols
2016-11-15 16:22 ` Dave Taht
2016-11-15 23:16 ` jb
2016-11-15 0:11 ` jb
2016-11-15 0:31 ` Dave Taht
2016-11-15 0:36 ` Jonathan Morton
2016-11-15 15:23 ` James Cloos
2016-11-15 15:43 ` Jan Ceuleers
2016-11-16 0:34 ` David Lang
2016-11-16 4:09 ` jb
2016-11-16 6:00 ` Stefan Alfredsson
2016-11-16 11:26 ` Stefan Alfredsson
2016-11-16 20:27 ` jb
2016-11-16 6:02 ` David Lang
[not found] ` <CY4PR04MB05665A2EFEB8CE55866C839A95BE0@CY4PR04MB0566.namprd04.prod.outlook.com>
2016-11-17 0:16 ` jb
2016-11-17 7:50 ` David Lang
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=CAA93jw78qX2Eze-8FKBO7++hnd_iPCWBQ3N006J+qbZzMhbbhw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.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