From: d@taht.net (Dave Täht)
To: bloat-devel@lists.bufferbloat.net
Subject: bloated vs debloated wireless test (iwllagn <-> wndr5700)
Date: Thu, 03 Feb 2011 08:57:55 -0700 [thread overview]
Message-ID: <87zkqdw1oc.fsf@cruithne.co.teklibre.org> (raw)
I did a little testing of my quick n' dirty wireless patch for the ath9k
on what I have.
The two devices are:
a netgear wndr 5700 running openwrt
a laptop with the iwllagn driver
Connected at 36Mbit, going from the (De-bloated)wndr 5700, using iperf
to saturate the link, ping times ranged from ~2ms to ~4ms.
In the opposite (bloated) direction from the lagn, they peaked at about 140ms.
Under contention (10 streams), I experienced about 4% packet loss on ping.
(I've never been so happy to see packet loss in my life)
The ath9k patch for openwrt - while still far from ideal - is here:
https://github.com/dtaht/Cruft/raw/master/bloat/558-ath9k_bufferbloat.patch
My test rig - which uses the babel protocol to make it easier to move
between routers and routed devices - is described (partially) here:
https://www.bufferbloat.net/projects/bloat/wiki/Dtaht_test_rig
--
Dave Taht
http://nex-6.taht.net
reply other threads:[~2011-02-03 15:58 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=87zkqdw1oc.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat-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