From: Sujith Manoharan <sujith@msujith.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] looking over ampdu stats
Date: Mon, 20 Jan 2014 08:57:40 +0530 [thread overview]
Message-ID: <21212.38828.910370.71395@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAA93jw4BjXJHSc1ibLP4zCGDMtucr=g7Jd_2US2QFTRZLT4W_w@mail.gmail.com>
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.
> 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.
Sujith
next prev parent reply other threads:[~2014-01-20 3:33 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 [this message]
2014-01-20 3:38 ` Dave Taht
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=21212.38828.910370.71395@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=cerowrt-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