All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hari Chandrakanthan <quic_haric@quicinc.com>, ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/2] wifi: cfg80211/mac80211: Add support to rx retry stats
Date: Wed, 27 Mar 2024 11:32:48 +0100	[thread overview]
Message-ID: <b9dfab64822bacf0cc72380c0de034b79d489668.camel@sipsolutions.net> (raw)
In-Reply-To: <14699537-99b2-e468-6a7b-7b721193400e@quicinc.com>

On Wed, 2024-03-27 at 15:39 +0530, Hari Chandrakanthan wrote:

> Fields such packet count, retries etc can be summed up for the MLD 
> representation and the existing NL attribute can be used for exposing
> the summed up value.

I think the existing attributes can also be used for per-link STA?

I'm kind of imagining that - once we actually do all of this properly -
the representation in nl80211 would be something like


STA 00:00:00:00:00:00
 - TX bytes: 123456
 - RX bytes: 654321
 - signal avg: -60 dBm     // picking the best of all links?
 ...
 - LINK 00:00:00:00:00:01
    - link ID: 10
    - TX bytes: 100000
    - RX bytes: 600000
    - signal avg: -60 dBm
 - LINK 00:00:00:00:00:02
    - link ID: 11
    - TX bytes: 23456
    - RX bytes: 54321
    - signal avg: -70 dBm

etc.

> But there are fields such as signal avg, bitrate etc which cannot be 
> summed up.

Right, but I guess we can pick 'best' for those, to at least have a
value? Or we could just not emit those attributes I guess, but not sure
if that's then all that useful?

> Should we expose such fields of each link STA through NL?

All of them, I guess?

I'm also imagining that we change the API from cfg80211 to the drivers
to get the *link* STA information, and do the summing up and/or "best"
selection there in cfg80211 itself. However, I am prepared to accept the
possibility that we may do _both_ in the API, if not all drivers can
even do all of the statistics per link. We should probably still have
the link STAs in the statistics in nl80211, but then they may not be
populated?

johannes

  reply	other threads:[~2024-03-27 10:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 13:45 [PATCH v2 0/2] wifi: cfg80211/ath12k: Add support to rx retry stats Hari Chandrakanthan
2024-03-19 13:45 ` [PATCH v2 1/2] wifi: cfg80211/mac80211: " Hari Chandrakanthan
2024-03-21 20:26   ` Jeff Johnson
2024-03-25 15:43   ` Johannes Berg
2024-03-27 10:09     ` Hari Chandrakanthan
2024-03-27 10:32       ` Johannes Berg [this message]
2024-03-27 15:02         ` Jeff Johnson
2024-03-27 15:07           ` Johannes Berg
2024-03-28 17:19             ` Hari Chandrakanthan
2024-03-28 17:54               ` Johannes Berg
2024-03-28 18:48                 ` Ben Greear
2024-03-19 13:45 ` [PATCH v2 2/2] wifi: ath12k: " Hari Chandrakanthan
2024-03-21 20:29   ` Jeff Johnson
2024-03-21 20:24 ` [PATCH v2 0/2] wifi: cfg80211/ath12k: " Jeff Johnson

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=b9dfab64822bacf0cc72380c0de034b79d489668.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_haric@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.