From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 3/4] station: knownnetworks: limit quick scans to 5 freqs per network
Date: Wed, 24 Jan 2024 12:21:25 -0600 [thread overview]
Message-ID: <36a3aa8a-ac08-44e7-91f7-73e094e69552@gmail.com> (raw)
In-Reply-To: <20240124134001.20453-3-prestwoj@gmail.com>
Hi James,
On 1/24/24 07:40, James Prestwood wrote:
> In very large network deployments there could be a vast amount of APs
> which could create a large known frequency list after some time once
> all the APs are seen in scan results. This then increases the quick
> scan time significantly, in the very worst case (but unlikely) just
> as long as a full scan.
>
> To help with this support in knownnetworks was added to limit the
> number of frequencies per network. Station will now only get 5
> recent frequencies per network making the maximum frequencies 25
> in the worst case (~2.5s scan).
>
> The magic values are now defines, and the recent roam frequencies
> was also changed to use this define as well.
Yep, I like it.
> ---
> src/knownnetworks.c | 9 ++++++---
> src/knownnetworks.h | 3 ++-
> src/station.c | 10 ++++++++--
> 3 files changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/src/knownnetworks.c b/src/knownnetworks.c
> index 6e549e02..fe0fce09 100644
> --- a/src/knownnetworks.c
> +++ b/src/knownnetworks.c
> @@ -518,7 +518,8 @@ struct network_info *known_networks_find(const char *ssid,
> }
>
> struct scan_freq_set *known_networks_get_recent_frequencies(
> - uint8_t num_networks_tosearch)
> + uint8_t num_networks_tosearch,
> + uint8_t freqs_per_network)
> {
> /*
> * This search function assumes that the known networks are always
> @@ -530,7 +531,7 @@ struct scan_freq_set *known_networks_get_recent_frequencies(
> const struct l_queue_entry *freq_entry;
> struct scan_freq_set *set;
>
> - if (!num_networks_tosearch)
> + if (!num_networks_tosearch || !freqs_per_network)
> return NULL;
>
> set = scan_freq_set_new();
> @@ -540,10 +541,12 @@ struct scan_freq_set *known_networks_get_recent_frequencies(
> network_entry = network_entry->next,
> num_networks_tosearch--) {
> const struct network_info *network = network_entry->data;
> + uint8_t freqs_found = 0;
>
> for (freq_entry = l_queue_get_entries(
> network->known_frequencies);
> - freq_entry; freq_entry = freq_entry->next) {
> + freq_entry && freqs_found < freqs_per_network;
> + freq_entry = freq_entry->next, freqs_found++) {
This is getting a bit unreadable. Maybe a while loop makes this look better?
freq_entry = l_queue_get_entries();
while (freq_entry && freqs_found < freq_per_network) {
...
freqs_found += 1;
freq_entry = freq_entry->next;
}
> const struct known_frequency *known_freq =
> freq_entry->data;
>
Regards,
-Denis
next prev parent reply other threads:[~2024-01-24 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 13:39 [PATCH v2 1/4] knownnetworks: pass scan_bss to known_network_add_frequency James Prestwood
2024-01-24 13:39 ` [PATCH v2 2/4] knownnetworks: sort known frequencies by BSS rank James Prestwood
2024-01-24 18:10 ` Denis Kenzior
2024-01-24 18:33 ` James Prestwood
2024-01-24 18:44 ` Denis Kenzior
2024-01-24 18:55 ` James Prestwood
2024-01-24 19:06 ` Denis Kenzior
2024-01-25 13:21 ` James Prestwood
2024-01-25 15:39 ` Denis Kenzior
2024-01-24 13:40 ` [PATCH v2 3/4] station: knownnetworks: limit quick scans to 5 freqs per network James Prestwood
2024-01-24 18:21 ` Denis Kenzior [this message]
2024-01-24 13:40 ` [PATCH v2 4/4] auto-t: add test for known frequency sorting/maximum James Prestwood
2024-01-24 18:16 ` [PATCH v2 1/4] knownnetworks: pass scan_bss to known_network_add_frequency 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=36a3aa8a-ac08-44e7-91f7-73e094e69552@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
/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