From: Jim Gettys <jg@freedesktop.org>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] General Bufferbloat Testing Document.
Date: Fri, 15 May 2015 12:16:56 -0400 [thread overview]
Message-ID: <CAGhGL2BzxO1=4705FEkZ74RjKLW-5J5DpBiSuwG2iySX1TLy0w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Even before I knew about the wonderful DSLreports bufferbloat test, I had
started working on a document to help people like that (e.g. Ookla)
understand how to do bufferbloat testing. The document also grew a bit
beyond that topic, by the time it was done....
The document is at:
https://docs.google.com/document/d/1z5NN4WRKQKK-RtxtKR__XIwkybvsKEmunek2Ezdw_90/edit?usp=sharing
Comments welcome.
It's intended long term home is the bufferbloat.net wiki, but I've found
Google doc's commenting feature really useful.
- Jim
[-- Attachment #2: Type: text/html, Size: 1200 bytes --]
next reply other threads:[~2015-05-15 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 16:16 Jim Gettys [this message]
2015-05-16 0:17 ` Stephen Hemminger
2015-05-16 8:55 ` Alan Jenkins
2015-05-16 11:43 ` Rich Brown
2015-05-18 1:58 ` Jim Gettys
2015-05-18 11:34 ` Rich Brown
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='CAGhGL2BzxO1=4705FEkZ74RjKLW-5J5DpBiSuwG2iySX1TLy0w@mail.gmail.com' \
--to=jg@freedesktop.org \
--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