From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 0/7] Reduce and optimize quick/roam scan frequencies
Date: Wed, 20 Dec 2023 05:11:53 -0800 [thread overview]
Message-ID: <20231220131200.267489-1-prestwoj@gmail.com> (raw)
For large network deployments with many APs the list of known
frequencies can grow rather large. Since there is no cap on
the number of frequencies for quick scans this results in quite
a long scan. Roam scans (with no neighbor report) do cap at 5
frequencies but this list isn't sorted or optimized to scan
the most recently used BSS's.
These patches separate the known frequency list into two
sections, first most recently used, then most recently
seen. That way previously connected BSS frequencies are scanned
ahead of others. This also caps the number of frequencies for
quick scans to 5 per network. This still could result in 25
frequencies scanned (worst case), but its probably not very
common for a device to see 5 separate SSID's it can connect to.
In most cases its one, maybe 2.
James Prestwood (7):
known_network: rename known_network_add_frequency
knownnetworks: add known_network_add_connected_frequency
network: call network_connected with BSS
network: add network_roamed
station: use network_roamed
auto-t: update known frequency test to check order
knownnetworks: limit 5 recent frequencies per network
autotests/testKnownNetworks/frequency_test.py | 122 +++++++++++++-----
autotests/testKnownNetworks/hw.conf | 10 +-
.../{ssidCCMP-2G.conf => ssidCCMP-2G-1.conf} | 0
.../testKnownNetworks/ssidCCMP-2G-2.conf | 8 ++
autotests/testKnownNetworks/ssidHotspot.conf | 2 +-
src/knownnetworks.c | 66 +++++++++-
src/knownnetworks.h | 6 +-
src/network.c | 19 ++-
src/network.h | 3 +-
src/station.c | 4 +-
10 files changed, 190 insertions(+), 50 deletions(-)
rename autotests/testKnownNetworks/{ssidCCMP-2G.conf => ssidCCMP-2G-1.conf} (100%)
create mode 100644 autotests/testKnownNetworks/ssidCCMP-2G-2.conf
--
2.34.1
next reply other threads:[~2023-12-20 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 13:11 James Prestwood [this message]
2023-12-20 13:11 ` [PATCH 1/7] known_network: rename known_network_add_frequency James Prestwood
2023-12-22 22:09 ` Denis Kenzior
2023-12-20 13:11 ` [PATCH 2/7] knownnetworks: add known_network_add_connected_frequency James Prestwood
2023-12-22 22:13 ` Denis Kenzior
2024-01-02 13:18 ` James Prestwood
2023-12-20 13:11 ` [PATCH 3/7] network: call network_connected with BSS James Prestwood
2023-12-20 13:11 ` [PATCH 4/7] network: add network_roamed James Prestwood
2023-12-20 13:11 ` [PATCH 5/7] station: use network_roamed James Prestwood
2023-12-20 13:11 ` [PATCH 6/7] auto-t: update known frequency test to check order James Prestwood
2023-12-20 13:12 ` [PATCH 7/7] knownnetworks: limit 5 recent frequencies per network James Prestwood
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=20231220131200.267489-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).