From: akolli@codeaurora.org
To: mbizon@freebox.fr
Cc: akolli@qti.qualcomm.com, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org,
linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH 2/2] ath10k: add per peer tx stats support for 10.2.4
Date: Fri, 01 Dec 2017 19:18:00 +0530 [thread overview]
Message-ID: <7792e2fb2c546d8745c65e48945f2535@codeaurora.org> (raw)
In-Reply-To: <1512125137.38490.70.camel@sakura.staff.proxad.net>
Hello,
Thanks for verifying the patch.
On 2017-12-01 16:15, Maxime Bizon wrote:
> On Thu, 2017-11-30 at 18:28 +0530, akolli@qti.qualcomm.com wrote:
>
> Hello,
>
>> Tested on QCA9880 with firmware version 10.2.4.70.48. This should also
>> work with firmware branch 10.2.4-1.0-00029
>
> I tried using your patch on 4.14 with firmware 10.2.4-1.0-00029
>
I will test update.
>> Parse peer stats from pktlog packets and update the tx rate
>> information
>> per STA. This way user space can query about transmit rate with iw:
>
> everything works ok, ath10k_update_per_peer_tx_stats() is called and
> ath10k_sta fields are updated correctly
>
> but tx bitrate is still 6 MBit/s in station dump
>
Hope CONFIG_MAC80211_DEBUGFS is enabled in your build.
Please Run ping traffic and see and 'station dump'
> # iw dev wlan1 station dump
> Station e4:42:a6:24:c8:95 (on wlan1)
> inactive time: 0 ms
> rx bytes: 222415
> rx packets: 1678
> tx bytes: 8511140
> tx packets: 5828
> tx retries: 0
> tx failed: 4
> rx drop misc: 2
> signal: -39 [-54, -56, -39] dBm
> signal avg: -39 [-53, -55, -39] dBm
> tx bitrate: 6.0 MBit/s
> rx bitrate: 360.0 MBit/s VHT-MCS 8 40MHz short GI VHT-NSS 2
> authorized: yes
> authenticated: yes
> associated: yes
> preamble: long
> WMM/WME: yes
> MFP: no
> TDLS peer: no
> DTIM period: 2
> beacon interval:96
> short slot time:yes
> connected time: 1136 seconds
>
> I see that ath10k does not implement ->dump_station callback, so which
> part of the code updates the generic "struct station_info" fields ?
>
> Am I missing a patch ?
>
Rate parameters are updated from below call,
.sta_statistics = ath10k_sta_statistics,
Thanks,
Anil.
next prev parent reply other threads:[~2017-12-01 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 12:58 [PATCH 0/2] ath10k: tx stats for 10.2.4 akolli
2017-11-30 12:58 ` [PATCH 1/2] ath10k: move pktlog_filter out of ath10k_debug akolli
2017-11-30 12:58 ` [PATCH 2/2] ath10k: add per peer tx stats support for 10.2.4 akolli
2017-11-30 16:14 ` Kalle Valo
2017-11-30 16:28 ` Toke Høiland-Jørgensen
2017-11-30 16:38 ` Kalle Valo
2017-12-01 4:23 ` akolli
2017-12-01 13:41 ` Toke Høiland-Jørgensen
2017-12-01 14:49 ` Kalle Valo
2017-12-01 15:29 ` Toke Høiland-Jørgensen
2017-12-01 15:45 ` Johannes Berg
2017-12-01 15:54 ` Toke Høiland-Jørgensen
2017-12-01 15:58 ` Johannes Berg
2017-12-02 9:53 ` Toke Høiland-Jørgensen
2017-12-01 10:45 ` Maxime Bizon
2017-12-01 13:48 ` akolli [this message]
2017-12-01 15:05 ` Maxime Bizon
2017-12-01 15:53 ` Christian Lamparter
2017-12-01 16:09 ` Maxime Bizon
2017-12-04 13:24 ` akolli
2017-12-04 14:23 ` Maxime Bizon
2017-12-05 5:26 ` akolli
2017-12-01 15:44 ` Kalle Valo
2017-12-04 11:20 ` akolli
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=7792e2fb2c546d8745c65e48945f2535@codeaurora.org \
--to=akolli@codeaurora.org \
--cc=akolli@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mbizon@freebox.fr \
/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).