From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel@lists.bufferbloat.net
Subject: still coping with zero packet loss over wireless
Date: Tue, 24 May 2011 14:46:59 +0000 [thread overview]
Message-ID: <BANLkTi=5ghAWh4zkkZ9Aht1CcFnzXJ2=Zg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
yesterday I finally got a chance to move a few dozen meters out of the lab
and test the latest build of uberwrt "capetown" and debloat-testing.
I'd hoped with the debloating techniques in place in capetown - reduced
buffers (4), reduced sw retries (2), hw retries (2, or so I thought) I'd
actually see some packet loss.
and what I saw instead, was pings that would take as long as 1.6 seconds to
complete, and zero packet loss until I moved completely out of range of the
router.
I never thought it would be so hard to lose a packet in my life!
Is there some system tunable, somewhere, in the linux wireless stack that
I've missed, in getting packets to actually fail in 10s of ms?
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 917 bytes --]
next reply other threads:[~2011-05-24 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 14:46 Dave Taht [this message]
2011-05-24 14:50 ` John W. Linville
2011-05-29 18:10 ` Dave Taht
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='BANLkTi=5ghAWh4zkkZ9Aht1CcFnzXJ2=Zg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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