All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: [PATCH v2 2/7] scan: rework BSS ranking
Date: Wed, 19 May 2021 10:00:47 -0500	[thread overview]
Message-ID: <59d5f498-f319-1dd1-755e-b8df66b48c0b@gmail.com> (raw)
In-Reply-To: <20210507202620.93540-2-prestwoj@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Hi James,

On 5/7/21 3:26 PM, James Prestwood wrote:
> It was observed that IWD's ranking for BSS's did not always
> end up with the fastest being chosen. This was due to IWD's
> heavy weight on signal strength. This is a decent way of ranking
> but even better is calculating a theoretical data rate which
> was also done and factored in. The problem is the data rate
> factor was always outdone by the signal strength.
> 
> Intead remove signal strength entirely as this is already taken
> into account with the data rate calculation. This also removes
> the check for rate IEs. If no IEs are found the parser will
> base the data rate soley on RSSI.
> 
> There were a few other factors removed which will be added back
> when ranking *networks* rather than BSS's. WPA version (or open)
> was removed as well as the privacy capability. These values really
> should not differ between BSS's in the same SSID and as such
> should be used for network ranking instead.
> ---
>   src/scan.c | 63 ++++++++++++++----------------------------------------
>   1 file changed, 16 insertions(+), 47 deletions(-)
> 
> v2:
>   * Added support for BSS's that did not have any rate IEs by
>     using the same ie_parse_data_rates
> 

I went ahead and applied the rest of this series (2-4).

Regards,
-Denis

  reply	other threads:[~2021-05-19 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 20:26 [PATCH v2 1/7] ie: fix ie_parse_data_rates to handle NULL James Prestwood
2021-05-07 20:26 ` [PATCH v2 2/7] scan: rework BSS ranking James Prestwood
2021-05-19 15:00   ` Denis Kenzior [this message]
2021-05-07 20:26 ` [PATCH v2 3/7] network: use WPA version and privacy for ranking James Prestwood
2021-05-07 20:26 ` [PATCH v2 4/7] station: autoconnect based on network, not BSS James Prestwood
2021-05-07 20:26 ` [PATCH v2 5/7] netdev: introduce [General].RoamThreshold5G James Prestwood
2021-05-07 20:26 ` [PATCH v2 6/7] doc: document [General].RoamThreshold5G James Prestwood
2021-05-10 15:13   ` Denis Kenzior
2021-05-07 20:26 ` [PATCH v2 7/7] test-runner: remove stale file after test James Prestwood
2021-05-10 15:09 ` [PATCH v2 1/7] ie: fix ie_parse_data_rates to handle NULL Denis Kenzior

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=59d5f498-f319-1dd1-755e-b8df66b48c0b@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.