-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PW_SID:819513] [v2,1/4] knownnetworks: pass scan_bss to known_network_add_frequency #302
base: workflow
Are you sure you want to change the base?
Conversation
This is taken care of by the individual cache items and if none exist, tar fails.
This prepares to store known frequencies sorted by BSS rank.
Currently a quick scan uses the entire known frequency list so ordering really doesn't matter but improvements will be made here to make quick scans "quicker" for large network deployments (with many known frequencies). To prepare for this the known frequency list has been changed to be sorted by BSS rank rather than most recently seen. This makes a lot more sense because IWD should prefer to scan frequencies that had higher ranked BSS's, not just frequencies that were scanned last on the most recent scan. As far as the disk sync goes the ranking is not included, but ordering is. This really isn't a limitation because when IWD starts up there isn't any guarantee its in the same physical location so old scan ranks are likely not valid anymore. The first set of scans will begin replacing the frequencies loaded from disk.
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.
Modify the existing frequency test to check that the ordering lines up with the ranking of the BSS. Add a test to check that quick scans limit the number of known frequencies.
Fetch PR Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches |
Fetch PR GitLint Make Distcheck Build - Configure Make Check Make Check w/Valgrind Incremental Build with patches Autotest Runner Clang Build |
263e09e
to
a7e34e0
Compare
cf3bcb6
to
46b3556
Compare
9eef0d5
to
d3b4175
Compare
f997c8d
to
a93a17f
Compare
68c71d2
to
43f4327
Compare
4170bb4
to
c067bc7
Compare
f10f2fc
to
c2be9ec
Compare
ebbbc93
to
089fa9a
Compare
2192e98
to
43a07cc
Compare
2c7b52e
to
58d64d4
Compare
68d5156
to
953fb5e
Compare
This prepares to store known frequencies sorted by BSS rank.
src/knownnetworks.c | 6 +++---
src/knownnetworks.h | 3 ++-
src/network.c | 6 +++---
3 files changed, 8 insertions(+), 7 deletions(-)