From: Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"devel@lists.open80211s.org" <devel@lists.open80211s.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Antonio Quartulli <antonio@open-mesh.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/7] mac80211: add get_expected_throughput API
Date: Fri, 18 Apr 2014 08:56:20 +0800 [thread overview]
Message-ID: <CAEFj987Hr4iUuHX-_nJN5AcHBLnAeJhhMX9UbqkGffTT+UQFLQ@mail.gmail.com> (raw)
In-Reply-To: <1397484205-20905-2-git-send-email-antonio@meshcoding.com>
Hi, Antonio
Do you know whether the calculation of expected throughput in minstrel
and minstrel_ht are both the same?
Any explanation on how the expected throughput is calculated?
---
Chun-Yeow
On Mon, Apr 14, 2014 at 10:03 PM, Antonio Quartulli
<antonio@meshcoding.com> wrote:
> From: Antonio Quartulli <antonio@open-mesh.com>
>
> Add get_expected_throughput() API to mac80211 so that each
> driver can implement its own version based on the RC
> algorithm they are using (might be using an HW RC algo).
> The API returns a value expressed in Mbps/100.
> This unit has been chosen because it is the same of the
> throughput returned by MinstrelHT.
>
> Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
> ---
> include/net/mac80211.h | 4 ++++
> net/mac80211/driver-ops.h | 13 +++++++++++++
> net/mac80211/trace.h | 32 ++++++++++++++++++++++++++++++++
> 3 files changed, 49 insertions(+)
>
> diff --git a/include/net/mac80211.h b/include/net/mac80211.h
> index a3044e1..0efe37c 100644
> --- a/include/net/mac80211.h
> +++ b/include/net/mac80211.h
> @@ -2761,6 +2761,9 @@ enum ieee80211_roc_type {
> * information in bss_conf is set up and the beacon can be retrieved. A
> * channel context is bound before this is called.
> * @leave_ibss: Leave the IBSS again.
> + *
> + * @get_expected_throughput: extract the expected throughput towards the
> + * specified station. The returned value is expressed in Mbps/100.
> */
> struct ieee80211_ops {
> void (*tx)(struct ieee80211_hw *hw,
> @@ -2954,6 +2957,7 @@ struct ieee80211_ops {
>
> int (*join_ibss)(struct ieee80211_hw *hw, struct ieee80211_vif *vif);
> void (*leave_ibss)(struct ieee80211_hw *hw, struct ieee80211_vif *vif);
> + u32 (*get_expected_throughput)(struct ieee80211_sta *sta);
> };
>
> /**
> diff --git a/net/mac80211/driver-ops.h b/net/mac80211/driver-ops.h
> index 5331582..84ee6c2 100644
> --- a/net/mac80211/driver-ops.h
> +++ b/net/mac80211/driver-ops.h
> @@ -1122,4 +1122,17 @@ static inline void drv_leave_ibss(struct ieee80211_local *local,
> trace_drv_return_void(local);
> }
>
> +static inline u32 drv_get_expected_throughput(struct ieee80211_local *local,
> + struct ieee80211_sta *sta)
> +{
> + u32 ret = 0;
> +
> + trace_drv_get_expected_throughput(sta);
> + if (local->ops->get_expected_throughput)
> + ret = local->ops->get_expected_throughput(sta);
> + trace_drv_return_u32(local, ret);
> +
> + return ret;
> +}
> +
> #endif /* __MAC80211_DRIVER_OPS */
> diff --git a/net/mac80211/trace.h b/net/mac80211/trace.h
> index a0b0aea..942f64b 100644
> --- a/net/mac80211/trace.h
> +++ b/net/mac80211/trace.h
> @@ -184,6 +184,20 @@ TRACE_EVENT(drv_return_bool,
> "true" : "false")
> );
>
> +TRACE_EVENT(drv_return_u32,
> + TP_PROTO(struct ieee80211_local *local, u32 ret),
> + TP_ARGS(local, ret),
> + TP_STRUCT__entry(
> + LOCAL_ENTRY
> + __field(u32, ret)
> + ),
> + TP_fast_assign(
> + LOCAL_ASSIGN;
> + __entry->ret = ret;
> + ),
> + TP_printk(LOCAL_PR_FMT " - %u", LOCAL_PR_ARG, __entry->ret)
> +);
> +
> TRACE_EVENT(drv_return_u64,
> TP_PROTO(struct ieee80211_local *local, u64 ret),
> TP_ARGS(local, ret),
> @@ -1499,6 +1513,24 @@ DEFINE_EVENT(local_sdata_evt, drv_leave_ibss,
> TP_ARGS(local, sdata)
> );
>
> +TRACE_EVENT(drv_get_expected_throughput,
> + TP_PROTO(struct ieee80211_sta *sta),
> +
> + TP_ARGS(sta),
> +
> + TP_STRUCT__entry(
> + STA_ENTRY
> + ),
> +
> + TP_fast_assign(
> + STA_ASSIGN;
> + ),
> +
> + TP_printk(
> + STA_PR_FMT, STA_PR_ARG
> + )
> +);
> +
> /*
> * Tracing for API calls that drivers call.
> */
> --
> 1.8.3.2
>
next prev parent reply other threads:[~2014-04-18 0:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 14:03 [PATCH 1/7] cfg80211: export expected throughput through get_station() Antonio Quartulli
2014-04-14 14:03 ` [PATCH 2/7] mac80211: add get_expected_throughput API Antonio Quartulli
2014-04-14 18:00 ` [B.A.T.M.A.N.] " Bastian Bittorf
2014-04-18 0:56 ` Yeoh Chun-Yeow [this message]
2014-04-18 6:19 ` Antonio Quartulli
2014-04-25 15:44 ` Johannes Berg
2014-05-14 21:09 ` Antonio Quartulli
2014-04-14 14:03 ` [PATCH 3/7] mac80211: add new RC API to retrieve expected throughput Antonio Quartulli
2014-04-25 15:45 ` Johannes Berg
2014-05-14 21:14 ` Antonio Quartulli
2014-04-14 14:03 ` [PATCH 4/7] mac80211: export expected throughput in set_sta_info() Antonio Quartulli
2014-04-14 14:03 ` [PATCH 5/7] mac80211: minstrel - implement get_expected_throughput() API Antonio Quartulli
2014-04-25 15:46 ` Johannes Berg
2014-04-25 15:47 ` Antonio Quartulli
2014-04-14 14:03 ` [PATCH 6/7] mac80211: minstrel_ht " Antonio Quartulli
2014-04-14 14:03 ` [PATCH 7/7] cfg80211: implement cfg80211_get_station cfg80211 API Antonio Quartulli
2014-04-25 15:46 ` Johannes Berg
2014-05-14 21:15 ` Antonio Quartulli
2014-04-25 15:44 ` [PATCH 1/7] cfg80211: export expected throughput through get_station() Johannes Berg
2014-05-14 21:27 ` 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=CAEFj987Hr4iUuHX-_nJN5AcHBLnAeJhhMX9UbqkGffTT+UQFLQ@mail.gmail.com \
--to=yeohchunyeow@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).