From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cake vs everything test run
Date: Sat, 16 Apr 2016 20:52:30 -0700 [thread overview]
Message-ID: <CAA93jw6XVtxXYtgXL8bJDUrnC8xv2r9VX7cysB6WBrJTcY-sMA@mail.gmail.com> (raw)
I am trying to do a better job of keeping a notebook, data, and graphs
in an easier
to read format - so, for example, see "cake vs everything"
http://blog.cerowrt.org/
or the latest dql on wifi results, off the same url.
and at the same time, I'd prefer to keep the conversation on the
mailing lists, or in github's issues page.
There are some really puzzling results I got on the single queue aqms
on that test run.
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
reply other threads:[~2016-04-17 3:52 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6XVtxXYtgXL8bJDUrnC8xv2r9VX7cysB6WBrJTcY-sMA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@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