Historic archive of defunct list cerowrt-commits@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: noreply@github.com
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 579447: Wireless QFQ tests.
Date: Mon, 2 Jan 2012 03:02:20 -0800	[thread overview]
Message-ID: <20120102110220.D97C14252A@smtp1.rs.github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/dtaht/deBloat

  Commit: 579447684ffdb512a9168b86b0515ae38335ab26
      https://github.com/dtaht/deBloat/commit/579447684ffdb512a9168b86b0515ae38335ab26
  Author: Dave Taht <d@taht.net>
  Date:   2012-01-02 (Mon, 02 Jan 2012)

  Changed paths:
    A test/results/wirelessqfqvspfifo.org

  Log Message:
  -----------
  Wireless QFQ tests.

The data is REALLY noisy and I need to run for a much longer time,
and come up with a good way to plot the results.

That said, QFQ has an average ping time of about 70ms vs 110 for pfifo_fast.

I suspect that using two (thoroughly debloated) ath9k cards will work
better - the laptop has an iwl which is known to be problematic.

And I need to vary some more variables.



                 reply	other threads:[~2012-01-02 11:02 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120102110220.D97C14252A@smtp1.rs.github.com \
    --to=noreply@github.com \
    --cc=cerowrt-commits@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