From: Dave Taht <dave.taht@gmail.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] looking over ampdu stats
Date: Sun, 19 Jan 2014 22:38:09 -0500 [thread overview]
Message-ID: <CAA93jw6qhsH1epKH6P47SagidHpe4_8cNk7FCF=tWT9bR=bOtA@mail.gmail.com> (raw)
In-Reply-To: <21212.38828.910370.71395@gargle.gargle.HOWL>
On Sun, Jan 19, 2014 at 10:27 PM, Sujith Manoharan <sujith@msujith.org> wrote:
> Dave Taht wrote:
>> in my tests, we almost never see more than 2 AMPDUs stacked up. (just
>> running netperf, not rrul).
>
> 2 is the minimum queue depth to aggregate packets. From ath9k.h:
> #define ATH_AGGR_MIN_QDEPTH 2
>
>> This could be the fault of the client device I'm using...
>
> This is not a bug with the client.
Gotcha. I went later (at felix's urging) to look at the rc_stats
and that showed some decent averages for the actual number of
packets in the AMPDU. Never managed to get it much above 11,
regardless of what I set be_qlen to...
>
>> cat /sys/kernel/debug/ieee80211/phy1/ath9k/queues
>>
>> (note: have set the default be_qlen to the default here)
>>
>> (VO): qnum: 0 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
>> (VI): qnum: 1 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
>> (BE): qnum: 2 qdepth: 3 ampdu-depth: 2 pending: 60 stopped: 0
>> (BK): qnum: 3 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
>> (CAB): qnum: 8 qdepth: 0 ampdu-depth: 0 pending: 0 stopped: 0
>
> qlen will not affect the minimum aggregate threshold, so adjusting
> be_qlen will not affect aggregation.
Well, it sort of does (or used to) in that cero holds this value low (12)
to minimize latency. While this costs some throughput it seems to help
in low rate situations.
>
> Sujith
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2014-01-20 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 17:20 Dave Taht
2014-01-20 3:27 ` Sujith Manoharan
2014-01-20 3:38 ` Dave Taht [this message]
2014-01-20 3:55 ` Sujith Manoharan
2014-01-20 15:09 ` David P. Reed
2014-01-20 15:35 ` Sujith Manoharan
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='CAA93jw6qhsH1epKH6P47SagidHpe4_8cNk7FCF=tWT9bR=bOtA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=sujith@msujith.org \
/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