2018-06-14 9:50 GMT+02:00 Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx>: > On 6/13/2018 5:10 PM, Toke Høiland-Jørgensen wrote: >> >> Tamizh Chelvam Raja <tamizhr@xxxxxxxxxxxxxxxx> writes: >> >>>> This patchsets introduced new NL command and api to support >>>> configuring txrate threshold for the connected stations and api to >>>> notify userspace application upon crossing the configured txrate >>>> threshold. >>>> This will be useful for the application which requires station's >>>> current capability change information. >>> >>> >>> What is the intended use case? Asking mostly out of curiosity :) >> >> >>> [Tamizh] This is to monitor txrate change for a station. By notifying >>> userspace when the txrate for a station goes out of configured >>> threshold, It can take steering decisions on the particular station. >> Do we really need kernel notification for that? You can simple monitor all this information same way iw station dump show. As a metric use tx/rx bitrate, signal or even expected throughput. Maybe small patch that will average tx/rx bitrate for few seconds (additional fields in station dump) could be helpful here. BR Janusz >> >> Yeah, I got that part. I was curious as to what (userspace) application >> you were planning to use this for? I.e., what kind of steering >> decisions? :) > > > It sounds like network initiated handover as opposed to station roaming. > Suspect the user-space application referred to here is a proprietary > application. At plumbers conf I attended a couple of years ago there was an > idea to have a network management application controlling multiple hostapd > instances for this type of functionality, but not sure if that project ever > got of the ground. > > Regards, > Arend > -- Janusz Dziedzic
