From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
"Mat Ford (Google+)"
<reply-110278001342819324593@profiles.google.com>
Subject: [Bloat] very nice article on the new dslreports test
Date: Mon, 27 Apr 2015 10:19:41 -0700 [thread overview]
Message-ID: <CAA93jw4vAiYcc-b23xpZqYWasKVRPn2TGw8HcBg2n6_jUwq5rA@mail.gmail.com> (raw)
http://www.internetsociety.org/blog/tech-matters/2015/04/measure-your-bufferbloat-new-browser-based-tool-dslreports
thx mat!
In reading that it occurred to me that by the bufferbloat community
actually using the test with systems with the bufferbloat fixes in
them, we'd be skewing the results.
It would be kind of nice to be able to attach an addendum or
additional notes to the test result - say with a drop down like:
Queue management technology: [none, fifo, qos, red, sfq, codel,
fq_codel, cake, pie, custom]
and comments field.
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
reply other threads:[~2015-04-27 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw4vAiYcc-b23xpZqYWasKVRPn2TGw8HcBg2n6_jUwq5rA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=reply-110278001342819324593@profiles.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