From: akolli@codeaurora.org
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Antonio Quartulli <a@unstable.cc>, Felix Fietkau <nbd@nbd.name>,
Marek Lindner <mareklindner@neomailbox.ch>,
Johannes Berg <johannes.berg@intel.com>,
linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH v2] ath10k: Implement get_expected_throughput callback
Date: Wed, 28 Mar 2018 11:41:51 +0530 [thread overview]
Message-ID: <7428dc3685e146dca147805b6a1bc5d2@codeaurora.org> (raw)
In-Reply-To: <2322769.sx4MhzsvNg@bentobox>
On 2018-03-26 12:52, Sven Eckelmann wrote:
> On Freitag, 23. März 2018 19:37:14 CEST Anilkumar Kolli wrote:
>> +static u32 ath10k_get_expected_throughput(struct ieee80211_hw *hw,
>> + struct ieee80211_sta *sta)
>> +{
>> + struct ath10k_sta *arsta = (struct ath10k_sta *)sta->drv_priv;
>> +
>> + return ewma_sta_txrate_read(&arsta->ave_sta_txrate);
>> +}
>
> On Freitag, 23. März 2018 19:11:48 CEST akolli@codeaurora.org wrote:
>> > Antonio and Felix, please correct me when this statement is incorrect.
>> >
>> > The expected_throughput as initially implemented for minstrel(_ht) is
>> > not
>> > about the raw physical bitrate but about the throughput which is
>> > expected for
>> > things running on top of the wifi link. See
>> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cca674d47e59665630f3005291b61bb883015fc5
>> > for more details
>> >
>> > when I interpret your change correctly then your it doesn't get the
>> > information about packet loss or aggregation and doesn't do anything
>> > convert
>> > from raw physical rate to something the user could get see. It will
>> > just
>> > overestimate the throughput for ath10k links and thus give wrong
>> > information
>> > to routing algorithms. This could for example cause them to prefer
>> > links over
>> > ath10k based hw when mt76 would actually provide a significant better
>> > throughput.
>> >
>> > Beside that - why is the ave_sta_txrate only filled when with new
>> > information
>> > when someone requests the current expected_throughput via
>> > get_expected_throughput. I would have expected that it is filled
>> > everytime you
>> > get new information about the current rate from the firmware
>> > (ath10k_sta_statistics).
>> >
>> Yes. ideally it should be doing the rate avg. of all the sent packets.
>
> No, not the PHY rate average - but the "throughput avg". And the
> "ideally"
> here sounds a little bit like in "Our medical doctor would ideally not
> decapitate each patient but we have at least an MD".
>
The rate average and throughput are relative. no?
- Anil.
next prev parent reply other threads:[~2018-03-28 6:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 14:07 [PATCH v2] ath10k: Implement get_expected_throughput callback Anilkumar Kolli
2018-03-26 7:22 ` Sven Eckelmann
2018-03-28 6:11 ` akolli [this message]
2018-03-28 6:37 ` Sven Eckelmann
2018-04-13 2:22 ` Peter Oh
2018-04-13 13:48 ` Kalle Valo
2018-04-13 20:24 ` Peter Oh
2018-04-16 6:30 ` 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=7428dc3685e146dca147805b6a1bc5d2@codeaurora.org \
--to=akolli@codeaurora.org \
--cc=a@unstable.cc \
--cc=ath10k@lists.infradead.org \
--cc=johannes.berg@intel.com \
--cc=linux-wireless-owner@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=nbd@nbd.name \
--cc=sven.eckelmann@openmesh.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).