From: Ben Greear <greearb@candelatech.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: Felix Fietkau <nbd@openwrt.org>,
Oleksij Rempel <linux@rempel-privat.de>,
ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: [ath9k-devel] [PATCH RFC] ath9k: collect statistics about Rx-Dup and Rx-STBC packets
Date: Wed, 08 May 2013 09:07:38 -0700 [thread overview]
Message-ID: <518A784A.6040704@candelatech.com> (raw)
In-Reply-To: <20873.58246.410990.985421@gargle.gargle.HOWL>
On 05/07/2013 10:32 PM, Sujith Manoharan wrote:
> Felix Fietkau wrote:
>> The problem I have with the current stats is they're just an arbitrary
>> collection of random stuff that is probably useless for 99% of all
>> users. In many cases the way the stats are collected also makes the data
>> completely meaningless (e.g. because the source/destination address is
>> not taken into account).
>>
>> Why care about the number of packets on the air that were sent with a
>> specific rate flag? Why care about the number of beacons on the air
>> (with no filter on a set of APs or anything)? Or what about the number
>> of fragments received? To me it just looks like an incoherent set of
>> useless facts.
>
> Yes, having per-station statistics would be useful, mainly for RX and TX. Right
> now, all the counters are global and there is no way to find out how a
> particular station is performing, especially in AP mode. Since mac80211 gives us
> proper debugfs hooks for station addition/deletion, relevant stuff can be moved
> there.
>
> The 'recv' file used to be just for HW errors (DESC, CRC etc.), now it has various
> counters that should probably be node-specific.
>
> The 'xmit' file can be trimmed and information can be maintained per-station.
> This will be really useful in AP mode - especially for diagnosing aggregation, QoS, PS etc.
I think it's good to keep global counters too..otherwise it is going to be
a lot of work to gather per NIC stats, and since you would have to read for each
station, your stats might not be quite as atomic as they used to be.
But, I'm fine with adding per-station counters on top of the global
stats.
Thanks,
Ben
>
> Other than these two files, the rest are simple.
>
> Sujith
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-05-08 16:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 15:25 [PATCH RFC] ath9k: collect statistics about Rx-Dup and Rx-STBC packets Oleksij Rempel
2013-04-27 18:39 ` [PATCH v2] " Oleksij Rempel
2013-04-27 18:51 ` Adrian Chadd
2013-04-27 18:53 ` Oleksij Rempel
2013-04-27 19:06 ` Adrian Chadd
2013-04-27 19:13 ` Oleksij Rempel
2013-04-28 1:21 ` [ath9k-devel] " Felix Fietkau
2013-04-28 6:41 ` [PATCH v3] " Oleksij Rempel
2013-04-28 12:51 ` [PATCH RFC] " Felix Fietkau
2013-04-28 14:13 ` Oleksij Rempel
2013-04-28 15:03 ` [ath9k-devel] " Oleksij Rempel
2013-04-28 19:19 ` Oleksij Rempel
2013-04-28 19:20 ` Felix Fietkau
2013-04-29 6:45 ` Wojciech Dubowik
2013-04-29 7:20 ` Oleksij Rempel
2013-04-28 14:54 ` Ben Greear
2013-04-28 15:08 ` Felix Fietkau
2013-04-28 15:15 ` Ben Greear
2013-04-28 15:32 ` Felix Fietkau
2013-05-08 5:32 ` Sujith Manoharan
2013-05-08 16:07 ` Ben Greear [this message]
2013-05-08 22:45 ` Adrian Chadd
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=518A784A.6040704@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=nbd@openwrt.org \
--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;
as well as URLs for NNTP newsgroup(s).