From: Sriram R <srirrama@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFCv2 1/2] nl80211: support per-rate/per-station statistics
Date: Sun, 12 Aug 2018 07:37:03 +0530 [thread overview]
Message-ID: <fcc0828ac58eaef422999547a2960ed5@codeaurora.org> (raw)
In-Reply-To: <1529065171.10037.16.camel@sipsolutions.net>
On 2018-06-15 17:49, Johannes Berg wrote:
> On Mon, 2018-05-28 at 19:04 +0530, Sriram R wrote:
>> Per-rate/per-station statistics can be desirable to have but they're
>> quite expensive (keeping the four counters for each rate would take
>> close to 4k of memory per station only for VHT MCSes for a moderately
>> capable VHT chip (with 2 spatial streams and 80MHz support) so it's
>> not a good idea to keep all of this in the kernel.
>>
>> Instead, this API provides a way for interested clients in userspace
>> to subscribe to such statistics. When supported by a driver, it can
>> then start collecting the data only when subscribers exist. To avoid
>> the kernel's data collection becoming too big, it can send out the
>> data at any point in time, for example to limit the counters to u16
>> internally and send it out when they're close to reaching the limit,
>> or to keep a hash table and sending it out when too many collisions
>> occur. Userspace can then keep track of the full state.
>>
>> Based on below implementation by Johannes Berg
>> <johannes@sipsolutions.net>
>> http://thread.gmane.org/gmane.linux.kernel.wireless.general/133172
>> with following changes,
>
> Err, that's pretty much an exact copy of my patch ...
>
> You should keep the author attribution and signed-off-by, and if you
> want your work to be separately attributed then just put the changes
> you
> made into (a) separate patch(es).
Sure! I'll correct this in my next revision.
>
>> 1. Allow rx bytes stats to be collected
>
> This seems OK.
>
>> 2. Rate info sent to userspace is encoded into 32bit value
>
> This I don't like at all. It's fine for the internal representation,
> and
> I know I did something like that in mac80211 (though I guess at the
> time
> it was only 16 bit), but it's not OK for the userspace representation.
>
> I just merged patches to support HE in the userspace representation,
> and
> that's properly taken into account in struct rate_info which I had here
> in my version of the patch.
Okay Johannes. I'll revert this in my next revision.
>
> johannes
next prev parent reply other threads:[~2018-08-12 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 13:34 [RFCv2 0/2] nl80211/mac80211 Add support for per-rate rx statistics Sriram R
2018-05-28 13:34 ` [RFCv2 1/2] nl80211: support per-rate/per-station statistics Sriram R
2018-06-15 12:19 ` Johannes Berg
2018-08-12 2:07 ` Sriram R [this message]
2018-05-28 13:34 ` [RFCv2 2/2] mac80211: Add support for per-rate rx statistics Sriram R
2018-06-15 12:25 ` Johannes Berg
2018-08-12 2:44 ` Sriram R
2018-08-28 9:00 ` Johannes Berg
2018-08-29 14:07 ` Sriram R
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=fcc0828ac58eaef422999547a2960ed5@codeaurora.org \
--to=srirrama@codeaurora.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).