From: "John W. Linville" <linville@tuxdriver.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: still coping with zero packet loss over wireless
Date: Tue, 24 May 2011 10:50:15 -0400 [thread overview]
Message-ID: <20110524145014.GA2504@tuxdriver.com> (raw)
In-Reply-To: <BANLkTi=5ghAWh4zkkZ9Aht1CcFnzXJ2=Zg@mail.gmail.com>
On Tue, May 24, 2011 at 02:46:59PM +0000, Dave Taht wrote:
> 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?
Not one of which I am aware. That sort of thing is going to depend
quite a bit on the hardware itself, and it's driver. Maybe some
ath9k folk can comment?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-05-24 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 14:46 Dave Taht
2011-05-24 14:50 ` John W. Linville [this message]
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=20110524145014.GA2504@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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