Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] the iwl driver sucks
Date: Sun, 9 Dec 2012 18:18:34 +0100	[thread overview]
Message-ID: <CAA93jw6qb2ZNMhab+3ULtJSNP4MbYQ4mJ=AtZU_TQ3xHGY=95w@mail.gmail.com> (raw)

I am happy to report that ad-hoc mode (used by cero in mesh networking
mode) still works in 3.6.9-5.

On the other hand the iwl driver in linux 3.6.8 is nearly unusable in
paris, generically, on my laptop. I have no idea why, I just want to
get an ath9k chip into it so I don't have to deal with it.... (it
takes 2 minutes or more to send an email via google, IF it succeeds.
I'm now 10 minutes into downloading richard's preso with only 320k
downloaded so far)

I did some rrul experiments on the adhoc interfaces today that were
very interesting.

One result was that in good conditions I'd get 100Mbit total,
bidirectionally, with rrul, with ath9k set to 128 packets, and could
see tcp global synchronization with pfifo fast, and fq_codel had very
little visible effect. uploads were at about 82Mbit and down 24. ~30ms
median RTT latency. I also saw a really neat one where BE and BK
traffic underwent priority inversion for a while.

With ath9k set to 2, and fq_codel I'd get about 16/13 and ~10ms median
RTT latency. So... far less throughput, but a vastly better up/down
ratio - and far less latency.

under bad conditions (router in the microwave for shielding), oh...
my... god... at 128 ath9k buffers... I don't want to talk about it.

-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

                 reply	other threads:[~2012-12-09 17:18 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='CAA93jw6qb2ZNMhab+3ULtJSNP4MbYQ4mJ=AtZU_TQ3xHGY=95w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@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