| Message ID | 1457508003-16700-1-git-send-email-mohammed@qca.qualcomm.com (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
On Wed, 2016-03-09 at 12:50 +0530, Mohammed Shafi Shajakhan wrote: > > + * @rx_duration: approximate total air time(usecs) for all the > frames from a > + * connected client I don't see why this should be restricted to "connected clients". The same value could be used for a mesh peer. Or TDLS peer. Or the AP on a managed connection. Or all the other types of STA. johannes
On Wed, Mar 09, 2016 at 10:30:03AM +0100, Johannes Berg wrote: > On Wed, 2016-03-09 at 12:50 +0530, Mohammed Shafi Shajakhan wrote: > > > > + * @rx_duration: approximate total air time(usecs) for all the > > frames from a > > + * connected client > > I don't see why this should be restricted to "connected clients". The > same value could be used for a mesh peer. Or TDLS peer. Or the AP on a > managed connection. Or all the other types of STA. [shafi] Please suggest if this is ok ? I will be thankful if you can suggest a better one if this is not ok * @rx_duration: approximate total air time(usecs) for all the frames from a peer regards, shafi
On Wed, 2016-03-09 at 15:08 +0530, Mohammed Shafi Shajakhan wrote: > [shafi] Please suggest if this is ok ? I will be thankful > if you can suggest a better one if this is not ok > > * @rx_duration: approximate total air time(usecs) for all the > frames from a peer > That seems fine. We should perhaps specify the meaning of "air time" though. Is it allocated NAV time, or is it just time in which there was energy? With or without any IFS? johannes
Hi Johannes, On Wed, Mar 09, 2016 at 10:58:08AM +0100, Johannes Berg wrote: > On Wed, 2016-03-09 at 15:08 +0530, Mohammed Shafi Shajakhan wrote: > > > [shafi] Please suggest if this is ok ? I will be thankful > > if you can suggest a better one if this is not ok > > > > * @rx_duration: approximate total air time(usecs) for all the > > frames from a peer > > > > That seems fine. We should perhaps specify the meaning of "air time" > though. Is it allocated NAV time, or is it just time in which there was > energy? With or without any IFS? > [shafi] ath10k implementation is based on PPDU duration calculation and it does not includes any IFS duration. So 'Energy' (time spent by the radio on receiving frames from a particular peer) makes more sense right ? regards, shafi
On Wed, 2016-03-09 at 16:22 +0530, Mohammed Shafi Shajakhan wrote: > > [shafi] ath10k implementation is based on PPDU duration calculation > and it does not includes any IFS duration. > > So 'Energy' (time spent by the radio on receiving frames from a > particular peer) makes more sense right ? > Fine with me, perhaps just saying "aggregate PPDU duration" would be a good thing? johannes
On Wed, Mar 09, 2016 at 12:18:25PM +0100, Johannes Berg wrote: > On Wed, 2016-03-09 at 16:22 +0530, Mohammed Shafi Shajakhan wrote: > > > > [shafi] ath10k implementation is based on PPDU duration calculation > > and it does not includes any IFS duration. > > > > So 'Energy' (time spent by the radio on receiving frames from a > > particular peer) makes more sense right ? > > > > Fine with me, perhaps just saying "aggregate PPDU duration" would be a > good thing? > [shafi] thanks johannes, fine with me and I also confirmed with the person who implemented this for ath10k, she is also fine with this definition as well. I will send a v3 updating the same as below: "@rx_duration: aggregate PPDU duration(usecs) for all the frames from a peer" regards shafi
diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h index 9bcaaf7..7897162 100644 --- a/include/net/cfg80211.h +++ b/include/net/cfg80211.h @@ -1060,11 +1060,13 @@ struct cfg80211_tid_stats { * @rx_beacon: number of beacons received from this peer * @rx_beacon_signal_avg: signal strength average (in dBm) for beacons received * from this peer + * @rx_duration: approximate total air time(usecs) for all the frames from a + * connected client * @pertid: per-TID statistics, see &struct cfg80211_tid_stats, using the last * (IEEE80211_NUM_TIDS) index for MSDUs not encapsulated in QoS-MPDUs. */ struct station_info { - u32 filled; + u64 filled; u32 connected_time; u32 inactive_time; u64 rx_bytes; @@ -1103,6 +1105,7 @@ struct station_info { u32 expected_throughput; u64 rx_beacon; + u64 rx_duration; u8 rx_beacon_signal_avg; struct cfg80211_tid_stats pertid[IEEE80211_NUM_TIDS + 1]; }; diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h index 5b7b5eb..3de3975 100644 --- a/include/uapi/linux/nl80211.h +++ b/include/uapi/linux/nl80211.h @@ -2464,6 +2464,8 @@ enum nl80211_sta_bss_param { * TID+1 and the special TID 16 (i.e. value 17) is used for non-QoS frames; * each one of those is again nested with &enum nl80211_tid_stats * attributes carrying the actual values. + * @NL80211_STA_INFO_RX_DURATION: approximate total air time(usecs) for all the + * frames from a connected client * @__NL80211_STA_INFO_AFTER_LAST: internal * @NL80211_STA_INFO_MAX: highest possible station info attribute */ @@ -2500,6 +2502,7 @@ enum nl80211_sta_info { NL80211_STA_INFO_BEACON_RX, NL80211_STA_INFO_BEACON_SIGNAL_AVG, NL80211_STA_INFO_TID_STATS, + NL80211_STA_INFO_RX_DURATION, /* keep last */ __NL80211_STA_INFO_AFTER_LAST, diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c index d4786f2..a81c016 100644 --- a/net/wireless/nl80211.c +++ b/net/wireless/nl80211.c @@ -3719,7 +3719,7 @@ static int nl80211_send_station(struct sk_buff *msg, u32 cmd, u32 portid, goto nla_put_failure; #define PUT_SINFO(attr, memb, type) do { \ - if (sinfo->filled & BIT(NL80211_STA_INFO_ ## attr) && \ + if (sinfo->filled & (1ULL << NL80211_STA_INFO_ ## attr) && \ nla_put_ ## type(msg, NL80211_STA_INFO_ ## attr, \ sinfo->memb)) \ goto nla_put_failure; \ @@ -3745,6 +3745,7 @@ static int nl80211_send_station(struct sk_buff *msg, u32 cmd, u32 portid, PUT_SINFO(LLID, llid, u16); PUT_SINFO(PLID, plid, u16); PUT_SINFO(PLINK_STATE, plink_state, u8); + PUT_SINFO(RX_DURATION, rx_duration, u64); switch (rdev->wiphy.signal_type) { case CFG80211_SIGNAL_TYPE_MBM: