From: Johannes Berg <johannes@sipsolutions.net>
To: Saravana <saravanad@posedge.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: add debugfs file for last ack signal
Date: Wed, 28 Nov 2012 13:33:36 +0100 [thread overview]
Message-ID: <1354106016.9345.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50B5CA15.2080407@posedge.com>
On Wed, 2012-11-28 at 13:53 +0530, Saravana wrote:
> Add a debugfs file showing the signal strength
> of the ack frame that is received for the
> currently sent tx packet
>
> Signed-off-by: Saravana <saravanad@posedge.com>
> ---
> net/mac80211/debugfs_sta.c | 2 ++
> net/mac80211/sta_info.h | 2 ++
> net/mac80211/status.c | 2 ++
> 3 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/net/mac80211/debugfs_sta.c b/net/mac80211/debugfs_sta.c
> index 89281d2..1566941 100644
> --- a/net/mac80211/debugfs_sta.c
> +++ b/net/mac80211/debugfs_sta.c
> @@ -53,6 +53,7 @@ static const struct file_operations sta_ ##name## _ops = { \
> STA_FILE(aid, sta.aid, D);
> STA_FILE(dev, sdata->name, S);
> STA_FILE(last_signal, last_signal, D);
> +STA_FILE(last_ack_signal, last_ack_signal, D);
>
> static ssize_t sta_flags_read(struct file *file, char __user *userbuf,
> size_t count, loff_t *ppos)
> @@ -369,6 +370,7 @@ void ieee80211_sta_debugfs_add(struct sta_info *sta)
> DEBUGFS_ADD(dev);
> DEBUGFS_ADD(last_signal);
> DEBUGFS_ADD(ht_capa);
> + DEBUGFS_ADD(last_ack_signal);
>
> DEBUGFS_ADD_COUNTER(rx_packets, rx_packets);
> DEBUGFS_ADD_COUNTER(tx_packets, tx_packets);
> diff --git a/net/mac80211/sta_info.h b/net/mac80211/sta_info.h
> index 6835cea..dce7693 100644
> --- a/net/mac80211/sta_info.h
> +++ b/net/mac80211/sta_info.h
> @@ -250,6 +250,7 @@ struct sta_ampdu_mlme {
> * @rx_dropped: number of dropped MPDUs from this STA
> * @last_signal: signal of last received frame from this STA
> * @avg_signal: moving average of signal of received frames from this STA
> + * @last_ack_signal: signal of last received Ack frame from this STA
> * @last_seq_ctrl: last received seq/frag number from this STA (per RX queue)
> * @tx_filtered_count: number of frames the hardware filtered for this STA
> * @tx_retry_failed: number of frames that failed retry
> @@ -329,6 +330,7 @@ struct sta_info {
> unsigned long rx_dropped;
> int last_signal;
> struct ewma avg_signal;
> + int last_ack_signal;
> /* Plus 1 for non-QoS frames */
> __le16 last_seq_ctrl[IEEE80211_NUM_TIDS + 1];
>
> diff --git a/net/mac80211/status.c b/net/mac80211/status.c
> index 2d931ad..64dda41 100644
> --- a/net/mac80211/status.c
> +++ b/net/mac80211/status.c
> @@ -539,6 +539,8 @@ void ieee80211_tx_status(struct ieee80211_hw *hw, struct sk_buff *skb)
> sta->lost_packets = 0;
> }
> }
> + if (acked)
> + sta->last_ack_signal = info->status.ack_signal;
I'd prefer a blank line before the if
This patch was sent in a way that I could apply it. :-)
johannes
next prev parent reply other threads:[~2012-11-28 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 8:23 [RFC] mac80211: add debugfs file for last ack signal Saravana
2012-11-28 12:33 ` Johannes Berg [this message]
2012-11-28 12:38 ` Saravana
-- strict thread matches above, loose matches on Subject: below --
2012-11-28 12:48 Saravana
2012-11-28 12:54 ` Johannes Berg
2012-11-26 13:57 saravanad
2012-11-26 15:15 ` Johannes Berg
2012-11-28 7:08 ` Saravana
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=1354106016.9345.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=saravanad@posedge.com \
/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).