On 10/19/2018 11:25 AM, Steve deRosier wrote:
On Fri, Oct 19, 2018 at 10:34 AM Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:
While debugging rate-ctrl in ath10k, I found the amount of mpdus transmitted vs failed
ratio useful. Probably more useful than retries since retries could count an attempt at
80Mhz followed by HW trying a 40Mhz rate (afaik).
Is there a good way to report this up the stack in a useful manner? I currently only
get this stat for the first frame in an transmitted ampdu.
debugfs? Is it useful for someone working on it, like a sysadmin or
kernel programmer? Or is it useful for programs to know? In the
first case I'd say debugfs, in the second case I'd suggest it goes in
some tx stats structure that is reported by netlink.
Also, is it something that is given by (or should be given by) all
drivers, or is it very driver-specific?
I was hoping I could fit it into some existing stat. It is sort of like
retries, so that will be my first attempt.
By investigating an RF sniff, I notice the 9880 ath10k (with my fw
and driver, at least), will retransmit about 30% of the frames when running
at least one of my test cases (small udp frame transmit to AP that can only do about mcs5 or mcs7
reliably at 3x3 nss).
I'd like to report this stat in my wifi test tool if nothing else, but
likely other people would make use of it as well.
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
