From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Anilkumar Kolli <akolli@qti.qualcomm.com>,
"akolli@codeaurora.org" <akolli@codeaurora.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Daniel Jeang <dyjeong@qti.qualcomm.com>,
Yifeng Tu <yifeng@qti.qualcomm.com>
Subject: Re: [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4
Date: Tue, 21 Nov 2017 10:46:41 +0100 [thread overview]
Message-ID: <2639938.VraEUeHfYF@bentobox> (raw)
In-Reply-To: <566f915b-0dbc-573f-3a6a-95ecf571674a@dd-wrt.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Dienstag, 21. November 2017 10:00:20 CET Sebastian Gottschall wrote:
> maybe this one?
>
> i have this qca988x supporting tx/rx rate patch in my local tree. just
> need to extract it again
>
> ath10k: report per-station tx/rate rates to mac80211
This one sounds like https://patchwork.kernel.org/patch/8597341/ - and it is
something different (end is implementing get_expected_throughput "wrong" and
therefore overestimates the expected throughput extremely). This patch is
using the stuff from fw_stats to fill the station rx/tx information.
It is not the worst thing to do (I want(ed) to use something similar for my
purposes) but there is a special pktlog message on 10.2 which contains the
same information as the 10.4 HTT_10_4_T2H_MSG_TYPE_PEER_STATS.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-11-21 9:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 16:37 [PATCHv3 1/2] ath10k: add per peer htt tx stats support for 10.4 akolli
2016-11-23 19:40 ` [PATCHv3,1/2] " Kalle Valo
2017-05-11 8:40 ` [PATCHv3 1/2] " Sven Eckelmann
2017-11-17 11:06 ` Sven Eckelmann
2017-11-21 7:58 ` Kalle Valo
2017-11-21 8:00 ` Sebastian Gottschall
2017-11-21 8:06 ` Kalle Valo
2017-11-21 8:20 ` Sven Eckelmann
2017-11-21 8:40 ` Kalle Valo
2017-11-21 9:00 ` Sebastian Gottschall
2017-11-21 9:46 ` Sven Eckelmann [this message]
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=2639938.VraEUeHfYF@bentobox \
--to=sven.eckelmann@openmesh.com \
--cc=akolli@codeaurora.org \
--cc=akolli@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=dyjeong@qti.qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
--cc=yifeng@qti.qualcomm.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