On 2018-05-18 15:00, Johannes Berg wrote:
On Wed, 2018-05-16 at 10:04 +0530, Sriram R wrote:
But, I wanted to avoid,
1. Static indexing and memory allocation based on MCS count((8x3)24
entries for HT and (10x3)30 for VHT within allocated 36 entries) so
that
it's scalable.
Do you exp
On Wed, 2018-05-16 at 10:04 +0530, Sriram R wrote:
> But, I wanted to avoid,
> 1. Static indexing and memory allocation based on MCS count((8x3)24
> entries for HT and (10x3)30 for VHT within allocated 36 entries) so that
> it's scalable.
Do you expect that the rate control on the other s
On 2018-05-15 12:30, Johannes Berg wrote:
On Tue, 2018-05-15 at 10:47 +0530, Sriram R wrote:
This patchset adds support for the collection and propagating of
per-rate, per-station rx statistics when enabled by a userspace
application.
These statistics can be useful in understanding the qualit
Sriram R writes:
> This patchset adds support for the collection and propagating of
> per-rate, per-station rx statistics when enabled by a userspace
> application.
Why not report TX rate statistics as well, when it is available?
Minstrel already collects this, and it is available via debugfs (t
On Tue, 2018-05-15 at 10:47 +0530, Sriram R wrote:
> This patchset adds support for the collection and propagating of
> per-rate, per-station rx statistics when enabled by a userspace application.
>
> These statistics can be useful in understanding the quality of
> communication with our peers an