Allow userspace to enable fine timing measurement responder
functionality with configurable lci/civic parameters in AP mode.
This can be done at AP start or changing beacon parameters.
A new EXT_FEATURE flag is introduced for drivers to advertise
the capability.
Also nl80211 API support for
New bss param ftm_responder is used to notify the driver to
enable fine timing request (FTM) responder role in AP mode.
Plumb the new cfg80211 API for FTM responder statistics through to
the driver API in mac80211.
Signed-off-by: David Spinadel
Signed-off-by: Johannes Berg
Signed-off-by:
Configure fine timing measurement (FTM) responder role from the
ftm_responder bss param sent by mac80211. With FTM functionality
offloaded to firmware, adding the interface allows userspace
to enable FTM responder functionality. ath10k disables it at the
time of interface creation.
Supported FW:
Currently ftm_responder parameter in hostapd.conf is only used for fine
timing measurement (FTM) capability advertisement and actual control of
the functionality is with low-level device/driver. This leads to confusion
to the user when the capability advertisement is different from actual FTM
Peter Oh writes:
> Hi Toke,
>
>
> On 08/17/2018 04:32 AM, Toke Høiland-Jørgensen wrote:
>>
> Shift 6:
> wgong@wgong-Latitude-E5440-1:~/flent$ flent -H 192.168.1.7 -t
> "sk_pacing_shift6" tcp_nup --test-parameter upload_streams=1
> Does flent have options to set TOS or QoS queue
Kalle Valo writes:
> Anilkumar Kolli 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
Anilkumar Kolli 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,
I have detected that ath10k with strong iperf tests (both TCP and UDP,
In UDP it's much easier to make it happen, due lack of congestion
control), the kernel runs out of memory and starts to launch OOM
Killer.
The scenario in which this problem is replicated is as follows:
20 stations and an
Anilkumar Kolli writes:
> This patch adds per station tx statistics support.
>
> Per station tx stats include
> - pkts/bytes transmitted at all possible rates(mcs/nss/bw/gi).
> - ACK fails count
> - ampdu bytes/pkts transmitted at all possible rates(mcs/nss/bw/gi).
> - BA fails count
>
>
