From: Yuan-Chi Pang <fu3mo6goo@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix TX status reporting for ieee80211s
Date: Thu, 06 Sep 2018 17:45:04 +0800 [thread overview]
Message-ID: <1536227104.68915.5.camel@gmail.com> (raw)
In-Reply-To: <1536224269-69350-1-git-send-email-fu3mo6goo@gmail.com>
On Thu, 2018-09-06 at 16:57 +0800, Yuan-Chi Pang wrote:
> TX status reporting to ieee80211s is through
> ieee80211s_update_metric.
> There are two problems about ieee80211s_update_metric:
>
> 1. The purpose is to estimate the fail probability
> to a specific link. No need to restrict to data frame.
>
> 2. Current implementation does not work if wireless driver does not
> pass tx_status with skb.
>
> Fix this by removing ieee80211_is_data condition, passing
> ieee80211_tx_status directly to ieee80211s_update_metric, and
> putting it in both __ieee80211_tx_status and ieee80211_tx_status_ext.
>
> Signed-off-by: Yuan-Chi Pang <fu3mo6goo@gmail.com>
> ---
> net/mac80211/mesh.h | 2 +-
> net/mac80211/mesh_hwmp.c | 8 ++------
> net/mac80211/status.c | 4 +++-
> 3 files changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/net/mac80211/mesh.h b/net/mac80211/mesh.h
> index ee56f18..7ffe56a 100644
> --- a/net/mac80211/mesh.h
> +++ b/net/mac80211/mesh.h
> @@ -217,7 +217,7 @@ void mesh_rmc_free(struct ieee80211_sub_if_data
> *sdata);
> int mesh_rmc_init(struct ieee80211_sub_if_data *sdata);
> void ieee80211s_init(void);
> void ieee80211s_update_metric(struct ieee80211_local *local,
> - struct sta_info *sta, struct sk_buff
> *skb);
> + struct sta_info *sta, struct
> ieee80211_tx_status *st);
> void ieee80211_mesh_init_sdata(struct ieee80211_sub_if_data *sdata);
> void ieee80211_mesh_teardown_sdata(struct ieee80211_sub_if_data
> *sdata);
> int ieee80211_start_mesh(struct ieee80211_sub_if_data *sdata);
I received the comment of my previous submission that I should fix
indentation. But if I use the same indentation as before, I got "line
over 80 characters" warning by checkpatch. What should I do?
> diff --git a/net/mac80211/mesh_hwmp.c b/net/mac80211/mesh_hwmp.c
> index daf9db3..4286673 100644
> --- a/net/mac80211/mesh_hwmp.c
> +++ b/net/mac80211/mesh_hwmp.c
> @@ -295,15 +295,11 @@ int mesh_path_error_tx(struct
> ieee80211_sub_if_data *sdata,
> }
>
> void ieee80211s_update_metric(struct ieee80211_local *local,
> - struct sta_info *sta, struct sk_buff *skb)
> + struct sta_info *sta, struct ieee80211_tx_status
> *st)
> {
> - struct ieee80211_tx_info *txinfo = IEEE80211_SKB_CB(skb);
> - struct ieee80211_hdr *hdr = (struct ieee80211_hdr *) skb-
> >data;
> + struct ieee80211_tx_info *txinfo = st->info;
> int failed;
>
> - if (!ieee80211_is_data(hdr->frame_control))
> - return;
> -
> failed = !(txinfo->flags & IEEE80211_TX_STAT_ACK);
>
> /* moving average, scaled to 100.
> diff --git a/net/mac80211/status.c b/net/mac80211/status.c
> index 9a6d720..dfcd419 100644
> --- a/net/mac80211/status.c
> +++ b/net/mac80211/status.c
> @@ -811,7 +811,7 @@ static void __ieee80211_tx_status(struct
> ieee80211_hw *hw,
>
> rate_control_tx_status(local, sband, status);
> if (ieee80211_vif_is_mesh(&sta->sdata->vif))
> - ieee80211s_update_metric(local, sta, skb);
> + ieee80211s_update_metric(local, sta,
> status);
>
> if (!(info->flags & IEEE80211_TX_CTL_INJECTED) &&
> acked)
> ieee80211_frame_acked(sta, skb);
> @@ -972,6 +972,8 @@ void ieee80211_tx_status_ext(struct ieee80211_hw
> *hw,
> }
>
> rate_control_tx_status(local, sband, status);
> + if (ieee80211_vif_is_mesh(&sta->sdata->vif))
> + ieee80211s_update_metric(local, sta,
> status);
> }
>
> if (acked || noack_success) {
next prev parent reply other threads:[~2018-09-06 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 7:12 [PATCH] mac80211: fix TX status reporting for ieee80211s Yuan-Chi Pang
2018-09-03 8:33 ` Johannes Berg
2018-09-06 8:57 ` Yuan-Chi Pang
2018-09-06 9:45 ` Yuan-Chi Pang [this message]
2018-09-06 9:47 ` 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=1536227104.68915.5.camel@gmail.com \
--to=fu3mo6goo@gmail.com \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).