From: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Kalle Valo <kvalo@qca.qualcomm.com>
Subject: Re: [PATCH 1/2] ath10k: add accounting for the extended peer statistics
Date: Wed, 7 Dec 2016 11:58:24 +0530 [thread overview]
Message-ID: <20161207062824.GA3404@atheros-ThinkPad-T61> (raw)
In-Reply-To: <992a4e2676037a06f482cdbe2d3d39e287530be5.1480974623.git.chunkeey@googlemail.com>
Hi Christian,
On Mon, Dec 05, 2016 at 10:52:45PM +0100, Christian Lamparter wrote:
> The 10.4 firmware adds extended peer information to the
> firmware's statistics payload. This additional info is
> stored as a separate data field and the elements are
> stored in their own "peers_extd" list.
>
> These elements can pile up in the same way as the peer
> information elements. This is because the
> ath10k_wmi_10_4_op_pull_fw_stats() function tries to
> pull the same amount (num_peer_stats) for every statistic
> data unit.
>
> Fixes: 4a49ae94a448faa ("ath10k: fix 10.4 extended peer stats update")
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> drivers/net/wireless/ath/ath10k/debug.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/debug.c b/drivers/net/wireless/ath/ath10k/debug.c
> index 82a4c67f3672..4acd9eb65910 100644
> --- a/drivers/net/wireless/ath/ath10k/debug.c
> +++ b/drivers/net/wireless/ath/ath10k/debug.c
> @@ -399,6 +399,7 @@ void ath10k_debug_fw_stats_process(struct ath10k *ar, struct sk_buff *skb)
> * prevent firmware from DoS-ing the host.
> */
> ath10k_fw_stats_peers_free(&ar->debug.fw_stats.peers);
> + ath10k_fw_extd_stats_peers_free(&ar->debug.fw_stats.peers_extd);
[shafi] thanks for fixing this !
> ath10k_warn(ar, "dropping fw peer stats\n");
> goto free;
> }
> @@ -409,10 +410,12 @@ void ath10k_debug_fw_stats_process(struct ath10k *ar, struct sk_buff *skb)
> goto free;
> }
>
> + if (!list_empty(&stats.peers))
[shafi] sorry please correct me if i am wrong, for 'extended peer stats' we are checking
for normal 'peer stats' ? Is this the fix intended, i had started a build to
check your change and we will keep you posted, does this fix displaying
'rx_duration' in ath10k fw_stats.
> + list_splice_tail_init(&stats.peers_extd,
> + &ar->debug.fw_stats.peers_extd);
> +
> list_splice_tail_init(&stats.peers, &ar->debug.fw_stats.peers);
> list_splice_tail_init(&stats.vdevs, &ar->debug.fw_stats.vdevs);
> - list_splice_tail_init(&stats.peers_extd,
> - &ar->debug.fw_stats.peers_extd);
> }
>
> complete(&ar->debug.fw_stats_complete);
thanks,
shafi
next prev parent reply other threads:[~2016-12-07 6:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 21:52 [PATCH 1/2] ath10k: add accounting for the extended peer statistics Christian Lamparter
2016-12-05 21:52 ` [PATCH 2/2] ath10k: fix potential memory leak in ath10k_wmi_tlv_op_pull_fw_stats() Christian Lamparter
2016-12-30 9:11 ` [2/2] " Kalle Valo
2016-12-07 6:28 ` Mohammed Shafi Shajakhan [this message]
2016-12-13 12:41 ` [PATCH 1/2] ath10k: add accounting for the extended peer statistics Christian Lamparter
2016-12-14 7:33 ` Mohammed Shafi Shajakhan
2016-12-14 16:38 ` Christian Lamparter
2016-12-15 16:26 ` Mohammed Shafi Shajakhan
2016-12-15 16:43 ` Mohammed Shafi Shajakhan
2016-12-15 17:24 ` Christian Lamparter
2016-12-16 5:24 ` Mohammed Shafi Shajakhan
2016-12-17 17:46 ` [PATCH] ath10k: merge extended peer info data with existing peers info Christian Lamparter
2016-12-19 16:49 ` Mohammed Shafi Shajakhan
2016-12-19 16:58 ` Mohammed Shafi Shajakhan
2016-12-19 18:37 ` Christian Lamparter
2016-12-22 15:48 ` Mohammed Shafi Shajakhan
2016-12-22 17:58 ` Christian Lamparter
2016-12-29 14:35 ` Mohammed Shafi Shajakhan
2017-05-05 12:51 ` Kalle Valo
2016-12-29 14:11 ` [1/2] ath10k: add accounting for the extended peer statistics Kalle Valo
2016-12-30 14:35 ` Christian Lamparter
2016-12-30 14:47 ` Valo, Kalle
2017-01-03 5:28 ` Mohammed Shafi Shajakhan
2017-01-04 20:06 ` Christian Lamparter
2017-01-11 10:49 ` Valo, Kalle
2017-01-13 13:28 ` Kalle Valo
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=20161207062824.GA3404@atheros-ThinkPad-T61 \
--to=mohammed@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=kvalo@qca.qualcomm.com \
--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