On 04/13/2018 06:48 AM, Kalle Valo wrote:
Sven Eckelmann writes:
But of course, I cannot say much about how the rate control from QCA works and
in which form these information are already available.
If you want to know the average PHY rate then wouldn't it be
Sven Eckelmann writes:
> On Mittwoch, 28. März 2018 11:41:51 CEST ako...@codeaurora.org wrote:
> [...]
>> The rate average and throughput are relative. no?
>
> In the sense that rate has a tendency to affect the expected throughput -
> yes.
> But it is not like the
Hi Anilkumar,
On 03/27/2018 11:37 PM, Sven Eckelmann wrote:
On Mittwoch, 28. März 2018 11:41:51 CEST ako...@codeaurora.org wrote:
[...]
The rate average and throughput are relative. no?
Can you share the output number from your new function?
It may help us to understand a little bit more how
On Mittwoch, 28. März 2018 11:41:51 CEST ako...@codeaurora.org wrote:
[...]
> The rate average and throughput are relative. no?
In the sense that rate has a tendency to affect the expected throughput - yes.
But it is not like the expected throughput perfectly correlates with the rate
and you
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
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;
> +
> +
Enable support for 'drv_get_expected_throughput' callback.
Export expected throughput if available to cfg80211/nl80211.
Signed-off-by: Anilkumar Kolli
Signed-off-by: Tamizh chelvam
---
v2:
- update the avg for all the transmitted frames(Sven)
-