From: Anilkumar Kolli <akolli@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
linux-wireless-owner@vger.kernel.org
Subject: Re: [RFC v2] ath10k: report tx rate using ieee80211_tx_status()
Date: Tue, 21 Aug 2018 11:34:52 +0530 [thread overview]
Message-ID: <dbab2233f2fe01136ef827328deac61f@codeaurora.org> (raw)
In-Reply-To: <87y3hb8jtp.fsf@kamboji.qca.qualcomm.com>
On 2018-04-25 19:33, Kalle Valo wrote:
> Anilkumar Kolli <akolli@codeaurora.org> writes:
>
>> On 2018-04-24 13:32, Kalle Valo wrote:
>>> Anilkumar Kolli <akolli@codeaurora.org> writes:
>>>
>>>> Mesh path metric needs txrate information from ieee80211_tx_status()
>>>> call but in ath10k there is no mechanism to report tx rate
>>>> information
>>>> via ieee80211_tx_status(), the rate is only accessible via
>>>> sta_statiscs() op.
>>>>
>>>> Per peer stats has tx rate info available, this patch stores per
>>>> peer
>>>> last tx rate and updates the tx rate info structures in tx
>>>> completition.
>>>> The rate updated in ieee80211_tx_status() is not exactly for the
>>>> last
>>>> transmitted frame instead the rate is from one of the previous
>>>> frames.
>>>>
>>>> Per peer txrate information is updated through per peer statistics
>>>> and is available for QCA9888/QCA9984/QCA4019/QCA998X only
>>>>
>>>> Tested on QCA9984 with firmware-5.bin_10.4-3.5.3-00053
>>>> Tested on QCA998X with firmware-5.bin_10.2.4-1.0-00036
>>>>
>>>> Signed-off-by: Anilkumar Kolli <akolli@codeaurora.org>
>>>
>>> BTW, your name in patchwork is "akolli@codeaurora.org" but it should
>>> be
>>> "Anilkumar Kolli" and that's why my script uses the wrong name.
>>> Please
>>> fix it by registering to patchwork as it's possible to change your
>>> name
>>> during registration, but only one time. If that doesn't work then
>>> send a
>>> request to helpdesk@kernel.org and the admins will fix it.
>>
>> I registered and updated name in the patchwork website.
>
> It seems that your name still is "akolli@codeaurora.org" in the
> Submitter field:
>
> https://patchwork.kernel.org/patch/10353959/
>
> An example how it should look like:
>
> https://patchwork.kernel.org/patch/10359823/
>
> I think you need to contact helpdesk now and ask them to fix it.
>
>> Do I need to resend the patch ?
>
> No need to resend because of this.
Hi Kalle,
Do you have any comments on this RFC. Shall I submit as a patch ?
Thanks
Anil.
next prev parent reply other threads:[~2018-08-21 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 6:23 [RFC v2] ath10k: report tx rate using ieee80211_tx_status() Anilkumar Kolli
2018-04-24 8:02 ` Kalle Valo
2018-04-25 9:59 ` Anilkumar Kolli
2018-04-25 14:03 ` Kalle Valo
2018-08-21 6:04 ` Anilkumar Kolli [this message]
2018-08-21 7:46 ` Kalle Valo
2018-08-31 12:29 ` Kalle Valo
2018-08-31 14:22 ` Toke Høiland-Jørgensen
2018-09-03 5:37 ` Anilkumar Kolli
2018-09-03 10:13 ` Toke Høiland-Jørgensen
2018-09-03 10:19 ` Anilkumar Kolli
2018-09-03 10:18 ` Johannes Berg
2018-09-06 7:10 ` Anilkumar Kolli
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=dbab2233f2fe01136ef827328deac61f@codeaurora.org \
--to=akolli@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless-owner@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).