From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: devel@lists.open80211s.org,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
Antonio Quartulli <antonio@open-mesh.com>
Subject: Re: [B.A.T.M.A.N.] [RFCv2 1/6] cfg80211: export expected throughput through get_station()
Date: Mon, 31 Mar 2014 10:22:45 +0200 [thread overview]
Message-ID: <20140331082245.GC4311@lunn.ch> (raw)
In-Reply-To: <1396211704-4677-2-git-send-email-antonio@meshcoding.com>
On Sun, Mar 30, 2014 at 10:34:59PM +0200, Antonio Quartulli wrote:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> Users may need information about the expected throughput
> towards a given peer computed by the RC algorithm.
> Export such value through the get_station() API.
>
> This information is useful to the batman-adv module which
> will use it for its new metric computation.
>
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
> ---
> include/net/cfg80211.h | 63 ++++++++++++++++++++++++++++----------------------
> 1 file changed, 35 insertions(+), 28 deletions(-)
>
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index fb8afce..4c8ebe9 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -862,36 +862,38 @@ int cfg80211_check_station_change(struct wiphy *wiphy,
> * @STATION_INFO_NONPEER_PM: @nonpeer_pm filled
> * @STATION_INFO_CHAIN_SIGNAL: @chain_signal filled
> * @STATION_INFO_CHAIN_SIGNAL_AVG: @chain_signal_avg filled
> + * @STATION_INFO_EXPECTED_THROUGHPUT: @expected_throughput filled
> */
> enum station_info_flags {
> - STATION_INFO_INACTIVE_TIME = 1<<0,
> - STATION_INFO_RX_BYTES = 1<<1,
> - STATION_INFO_TX_BYTES = 1<<2,
> - STATION_INFO_LLID = 1<<3,
> - STATION_INFO_PLID = 1<<4,
> - STATION_INFO_PLINK_STATE = 1<<5,
> - STATION_INFO_SIGNAL = 1<<6,
> - STATION_INFO_TX_BITRATE = 1<<7,
> - STATION_INFO_RX_PACKETS = 1<<8,
> - STATION_INFO_TX_PACKETS = 1<<9,
> - STATION_INFO_TX_RETRIES = 1<<10,
> - STATION_INFO_TX_FAILED = 1<<11,
> - STATION_INFO_RX_DROP_MISC = 1<<12,
> - STATION_INFO_SIGNAL_AVG = 1<<13,
> - STATION_INFO_RX_BITRATE = 1<<14,
> - STATION_INFO_BSS_PARAM = 1<<15,
> - STATION_INFO_CONNECTED_TIME = 1<<16,
> - STATION_INFO_ASSOC_REQ_IES = 1<<17,
> - STATION_INFO_STA_FLAGS = 1<<18,
> - STATION_INFO_BEACON_LOSS_COUNT = 1<<19,
> - STATION_INFO_T_OFFSET = 1<<20,
> - STATION_INFO_LOCAL_PM = 1<<21,
> - STATION_INFO_PEER_PM = 1<<22,
> - STATION_INFO_NONPEER_PM = 1<<23,
> - STATION_INFO_RX_BYTES64 = 1<<24,
> - STATION_INFO_TX_BYTES64 = 1<<25,
> - STATION_INFO_CHAIN_SIGNAL = 1<<26,
> - STATION_INFO_CHAIN_SIGNAL_AVG = 1<<27,
> + STATION_INFO_INACTIVE_TIME = 1<<0,
> + STATION_INFO_RX_BYTES = 1<<1,
> + STATION_INFO_TX_BYTES = 1<<2,
> + STATION_INFO_LLID = 1<<3,
> + STATION_INFO_PLID = 1<<4,
> + STATION_INFO_PLINK_STATE = 1<<5,
> + STATION_INFO_SIGNAL = 1<<6,
> + STATION_INFO_TX_BITRATE = 1<<7,
> + STATION_INFO_RX_PACKETS = 1<<8,
> + STATION_INFO_TX_PACKETS = 1<<9,
> + STATION_INFO_TX_RETRIES = 1<<10,
> + STATION_INFO_TX_FAILED = 1<<11,
> + STATION_INFO_RX_DROP_MISC = 1<<12,
> + STATION_INFO_SIGNAL_AVG = 1<<13,
> + STATION_INFO_RX_BITRATE = 1<<14,
> + STATION_INFO_BSS_PARAM = 1<<15,
> + STATION_INFO_CONNECTED_TIME = 1<<16,
> + STATION_INFO_ASSOC_REQ_IES = 1<<17,
> + STATION_INFO_STA_FLAGS = 1<<18,
> + STATION_INFO_BEACON_LOSS_COUNT = 1<<19,
> + STATION_INFO_T_OFFSET = 1<<20,
> + STATION_INFO_LOCAL_PM = 1<<21,
> + STATION_INFO_PEER_PM = 1<<22,
> + STATION_INFO_NONPEER_PM = 1<<23,
> + STATION_INFO_RX_BYTES64 = 1<<24,
> + STATION_INFO_TX_BYTES64 = 1<<25,
> + STATION_INFO_CHAIN_SIGNAL = 1<<26,
> + STATION_INFO_CHAIN_SIGNAL_AVG = 1<<27,
> + STATION_INFO_EXPECTED_THROUGHPUT = 1<<28,
> };
Hi Antonio
> /**
> @@ -1013,6 +1015,9 @@ struct sta_bss_parameters {
> * @local_pm: local mesh STA power save mode
> * @peer_pm: peer mesh STA power save mode
> * @nonpeer_pm: non-peer mesh STA power save mode
> + * @expected_throughput: expected throughput as reported by the RC algorithm
> + * about the bitrate having the maximum throughput. This field can be filled
> + * only by drivers using Minstrel
> */
> struct station_info {
> u32 filled;
> @@ -1051,6 +1056,8 @@ struct station_info {
> enum nl80211_mesh_power_mode peer_pm;
> enum nl80211_mesh_power_mode nonpeer_pm;
>
> + u32 expected_throughput;
> +
It would be nice to comment on what the units are. I known from our
BATMAN V discussions, it is something odd.
Andrew
next prev parent reply other threads:[~2014-03-31 8:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 20:34 [B.A.T.M.A.N.] [RFCv2 0/6] Export the expected throughput Antonio Quartulli
2014-03-30 20:34 ` [B.A.T.M.A.N.] [RFCv2 1/6] cfg80211: export expected throughput through get_station() Antonio Quartulli
2014-03-31 8:22 ` Andrew Lunn [this message]
2014-03-31 8:46 ` Antonio Quartulli
2014-04-08 10:03 ` Johannes Berg
2014-04-10 16:22 ` Antonio Quartulli
2014-03-30 20:35 ` [B.A.T.M.A.N.] [RFCv2 2/6] mac80211: add new RC API to retrieve expected throughput Antonio Quartulli
2014-04-08 10:03 ` Johannes Berg
2014-04-10 15:46 ` Antonio Quartulli
2014-04-10 17:13 ` Johannes Berg
2014-04-11 7:03 ` Antonio Quartulli
2014-04-08 10:04 ` Johannes Berg
2014-04-10 15:53 ` Antonio Quartulli
2014-04-10 17:14 ` Johannes Berg
2014-04-11 11:30 ` Antonio Quartulli
2014-03-30 20:35 ` [B.A.T.M.A.N.] [RFCv2 3/6] mac80211: export expected throughput in set_sta_info() Antonio Quartulli
2014-03-30 20:35 ` [B.A.T.M.A.N.] [RFCv2 4/6] mac80211: minstrel - implement get_expected_throughput() API Antonio Quartulli
2014-03-31 8:49 ` Antonio Quartulli
2014-04-08 10:05 ` Johannes Berg
2014-04-10 15:54 ` Antonio Quartulli
2014-03-30 20:35 ` [B.A.T.M.A.N.] [RFCv2 5/6] mac80211: minstrel_ht " Antonio Quartulli
2014-03-30 20:35 ` [B.A.T.M.A.N.] [RFCv2 6/6] cfg80211: implement cfg80211_get_station cfg80211 API Antonio Quartulli
2014-04-08 10:06 ` Johannes Berg
2014-04-10 16:02 ` Antonio Quartulli
2014-04-10 17:12 ` Johannes Berg
2014-04-11 7:04 ` Antonio Quartulli
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=20140331082245.GC4311@lunn.ch \
--to=andrew@lunn.ch \
--cc=antonio@open-mesh.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=devel@lists.open80211s.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