From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: [patch 9/9] mac80211: implement station stats retrieval
Date: Thu, 25 Oct 2007 11:36:27 +0200 [thread overview]
Message-ID: <20071025093718.092951000@sipsolutions.net> (raw)
In-Reply-To: 20071025093618.440937000@sipsolutions.net
This implements the required cfg80211 callback in mac80211
to allow userspace to get station statistics.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
net/mac80211/cfg.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
--- linux-2.6.orig/net/mac80211/cfg.c 2007-10-24 11:35:58.552690568 +0200
+++ linux-2.6/net/mac80211/cfg.c 2007-10-24 11:36:00.982690568 +0200
@@ -571,6 +571,31 @@ static int ieee80211_change_station(stru
return 0;
}
+static int ieee80211_get_station(struct wiphy *wiphy, struct net_device *dev,
+ u8 *mac, struct station_stats *stats)
+{
+ struct ieee80211_local *local = wdev_priv(dev->ieee80211_ptr);
+ struct sta_info *sta;
+
+ sta = sta_info_get(local, mac);
+ if (!sta)
+ return -ENOENT;
+
+ /* XXX: verify sta->dev == dev */
+
+ stats->filled = STATION_STAT_INACTIVE_TIME |
+ STATION_STAT_RX_BYTES |
+ STATION_STAT_TX_BYTES;
+
+ stats->inactive_time = jiffies_to_msecs(jiffies - sta->last_rx);
+ stats->rx_bytes = sta->rx_bytes;
+ stats->tx_bytes = sta->tx_bytes;
+
+ sta_info_put(sta);
+
+ return 0;
+}
+
struct cfg80211_ops mac80211_config_ops = {
.add_virtual_intf = ieee80211_add_iface,
.del_virtual_intf = ieee80211_del_iface,
@@ -583,4 +608,5 @@ struct cfg80211_ops mac80211_config_ops
.add_station = ieee80211_add_station,
.del_station = ieee80211_del_station,
.change_station = ieee80211_change_station,
+ .get_station = ieee80211_get_station,
};
--
next prev parent reply other threads:[~2007-10-25 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 9:36 [patch 0/9] initial round of hostapd support patches Johannes Berg
2007-10-25 9:36 ` [patch 1/9] cfg80211/nl80211: introduce key handling Johannes Berg
2007-10-25 9:36 ` [patch 2/9] mac80211: support adding/removing keys via cfg80211 Johannes Berg
2007-10-25 9:36 ` [patch 3/9] mac80211: support getting key sequence counters " Johannes Berg
2007-10-25 9:36 ` [patch 4/9] cfg80211/nl80211: add beacon settings Johannes Berg
2007-10-25 9:42 ` Johannes Berg
2007-10-25 9:36 ` [patch 5/9] mac80211: add beacon configuration via cfg80211 Johannes Berg
2007-10-25 15:59 ` Luis R. Rodriguez
2007-10-26 10:37 ` Johannes Berg
2007-10-25 9:36 ` [patch 6/9] nl80211/cfg80211: station handling Johannes Berg
2007-10-25 15:46 ` Luis R. Rodriguez
2007-10-25 17:33 ` Michael Wu
2007-10-26 10:40 ` Johannes Berg
2007-10-25 9:36 ` [patch 7/9] mac80211: implement cfg80211s " Johannes Berg
2007-10-25 9:36 ` [patch 8/9] cfg80211/nl80211: implement station attribute retrieval Johannes Berg
2007-10-25 9:36 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-19 1:03 [PATCH 0/9] nl80211/cfg80211/mac80211 updates for AP mode Johannes Berg
2007-12-19 1:03 ` [PATCH 9/9] mac80211: implement station stats retrieval Johannes Berg
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=20071025093718.092951000@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 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).