linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tamizh chelvam <tamizhr@codeaurora.org>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: "Arend van Spriel" <arend.vanspriel@broadcom.com>,
	"Toke Høiland-Jørgensen" <toke@toke.dk>,
	"Tamizh Chelvam Raja" <tamizhr@qti.qualcomm.com>,
	johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/4] cfg80211/mac80211: Add support to configure and monitor txrate threshold
Date: Tue, 19 Jun 2018 12:58:11 +0530	[thread overview]
Message-ID: <793f824c63cfcfecf8e708d1ffc54c63@codeaurora.org> (raw)
In-Reply-To: <CAFED-jkWPMgpHvrp2xE4dtKmLW4DU8j34-_5Ss4rVoBGJi9rrQ@mail.gmail.com>

On 2018-06-15 17:16, Janusz Dziedzic wrote:
> 2018-06-14 9:50 GMT+02:00 Arend van Spriel 
> <arend.vanspriel@broadcom.com>:
>> On 6/13/2018 5:10 PM, Toke Høiland-Jørgensen wrote:
>>> 
>>> Tamizh Chelvam Raja <tamizhr@qti.qualcomm.com> 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.

In this case user space application need to fetch the station statistics 
periodically and parse those detail.
Let say AP has more number of stations(like more than 50) in all 
bands(2G and 5G), then the system overhead will be more for fetching the 
detail periodically.
But with this kernel notification we can avoid those overhead and more 
or less this is similar to the CQM(rssi, txe,..) notification in STA 
mode.

Thanks,
Tamizh.

> 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
>> 

      reply	other threads:[~2018-06-19  7:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 10:58 [PATCH 0/4] cfg80211/mac80211: Add support to configure and monitor txrate threshold Tamizh chelvam
2018-06-13 10:58 ` [PATCH 1/4] cfg80211: Add support to configure station specific " Tamizh chelvam
2018-06-29  9:44   ` Johannes Berg
2018-06-13 10:58 ` [PATCH 2/4] mac80211: Add api to configure low and high " Tamizh chelvam
2018-06-29  9:45   ` Johannes Berg
2018-06-13 10:58 ` [PATCH 3/4] cfg80211: Add support to notify station's txrate crossing event Tamizh chelvam
2018-06-29  9:46   ` Johannes Berg
2018-06-13 10:58 ` [PATCH 4/4] mac80211: Implement functionality to monitor txrate cross event for a station Tamizh chelvam
2018-06-29  9:47   ` Johannes Berg
2018-06-13 12:10 ` [PATCH 0/4] cfg80211/mac80211: Add support to configure and monitor txrate threshold Toke Høiland-Jørgensen
2018-06-13 14:24   ` Tamizh Chelvam Raja
2018-06-13 15:10     ` Toke Høiland-Jørgensen
2018-06-14  7:50       ` Arend van Spriel
2018-06-15 11:46         ` Janusz Dziedzic
2018-06-19  7:28           ` Tamizh chelvam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=793f824c63cfcfecf8e708d1ffc54c63@codeaurora.org \
    --to=tamizhr@codeaurora.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=janusz.dziedzic@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tamizhr@qti.qualcomm.com \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).