Re: [RFC 2/2] ath10k: Add QCA vendor command/attr support to filterneighbor BSS frames

[Karthikeyan Periyasamy <periyasa@codeaurora.org>]

On 2019-01-26 02:19, Johannes Berg wrote:
> 
> Sure. I guess my question was intended more along the lines of "how 
> much
> CPU impact would you be able to live with?" :-)

As much as no CPU impact.

> At the same time, what happens today actually? Do all frames from non-
> associated clients come up to the host? If so, is this not a problem 
> for
> all APs, not just ath10k?
> 

Today, without this patch. No frames from non-associated clients come up 
to the host in AP mode.

> And if they don't come up, what feature requires this? Sorry for the
> vague questions, but I'm not really sure what this is all about. If
> there's a need for these frames, wouldn't we need a generic way of
> enabling receiving them, and perhaps even signalling hostapd with them?

Steering application use this feature in their logical part of client 
steering.

This feature allow an application to configure filtering rules to 
capture from
stations that are active on the operating channel but not associated to 
this AP.
It also allow to get the statistics information of the configured non 
associated stations.

Ath10k driver use HW filter to capture other BSS frames and drop these 
packets
after collecting statistics information of configured non associated 
stations.

QCA vendor command/attr details:
https://w1.fi/cgit/hostap/commit/?id=6b21df0bb7a261ef890a02d1fef95ffa5ff54cfc


> Also, what are the statistics and what do you intend to use them for?

In this patch, we are providing the below information as a statistics of 
non associated stations.

- MAC address
- Last received signal strength
- Time stamp of the last received signal strength

Thanks,
Karthikeyan