From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] nl80211: support MSDU statistics
Date: Fri, 19 Dec 2014 12:05:32 +0100 [thread overview]
Message-ID: <1418987132.1889.4.camel@sipsolutions.net> (raw)
In-Reply-To: <1418919083-28297-1-git-send-email-johannes@sipsolutions.net> (sfid-20141218_171132_119479_078E1815)
> + * @rx_qos_msdu: QoS-MSDUs received from this station (per TID)
> + * @rx_nonqos_msdu: non-QoS-MSDUs received from this station
> + * @tx_qos_msdu: QoS-MSDUs sent to this station (per TID)
> + * @tx_nonqos_msdu: non-QoS-MSDUs sent to this station
Well, come to think of it, it looks like we'll probably want more
per-TID data in the future, I'll need at least retries and lost MSDUs.
As a consequence, I'm going to make this the other way around and have a
per-TID nesting (using idx 16 for non-QoS) and in there have the
different values. This will also affect the cfg80211 API.
johannes
prev parent reply other threads:[~2014-12-19 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 16:11 [PATCH 1/2] nl80211: support MSDU statistics Johannes Berg
2014-12-18 16:11 ` [PATCH 2/2] mac80211: provide per-TID RX/TX MSDU counters Johannes Berg
2014-12-19 11:05 ` Johannes Berg [this message]
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=1418987132.1889.4.camel@sipsolutions.net \
--to=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 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.