From: James Prestwood <prestwoj@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 0/4] Packet/beacon loss roaming improvements
Date: Thu, 2 Nov 2023 08:41:09 -0700 [thread overview]
Message-ID: <99451a2d-7b3d-4927-a733-a86e58c81a4d@gmail.com> (raw)
In-Reply-To: <424127a9-af47-4a15-91f1-ff97e7ceacc8@gmail.com>
Hi Denis,
>>
>> In theory only 5:
>> known_freq_set = known_networks_get_recent_frequencies(5);
>>
>
> No, that picks the top 5 most recently used networks. The known
> frequencies for each of the top 5 are added to the quick scan. This
> works okay most of the time, but we do not rotate out known frequencies,
> so if you have a network with lots of APs spread out over the spectrum,
> it might end up scanning quite a bit.
Ah, that is exactly the problem then.
I wonder if we should be limiting both known networks and frequencies in
those networks. We do push new frequencies in order that they are added
so it may be nice to just pick the first 5 or so in the queue. Then we'd
be capping 25 frequencies at most instead of the whole spectrum in the
worst case.
>
> Regards,
> -Denis
next prev parent reply other threads:[~2023-11-02 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 13:48 [PATCH 0/4] Packet/beacon loss roaming improvements James Prestwood
2023-10-30 13:48 ` [PATCH 1/4] station: rename ap_directed_roam to force_roam James Prestwood
2023-10-30 13:48 ` [PATCH 2/4] station: start roam on beacon loss event James Prestwood
2023-10-30 13:48 ` [PATCH 3/4] netdev: handle/send " James Prestwood
2023-10-30 13:48 ` [PATCH 4/4] station: rate limit packet loss roam scans James Prestwood
2023-10-30 14:48 ` Denis Kenzior
2023-10-30 15:00 ` [PATCH 0/4] Packet/beacon loss roaming improvements Denis Kenzior
2023-10-30 15:37 ` James Prestwood
2023-10-30 17:05 ` Denis Kenzior
2023-10-30 17:37 ` James Prestwood
2023-11-01 12:07 ` James Prestwood
2023-11-02 1:39 ` Denis Kenzior
2023-11-02 11:58 ` James Prestwood
2023-11-02 14:10 ` Denis Kenzior
2023-11-02 14:33 ` James Prestwood
2023-11-02 15:17 ` Denis Kenzior
2023-11-02 15:41 ` James Prestwood [this message]
2023-11-02 16:10 ` Denis Kenzior
2023-11-02 16:13 ` 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=99451a2d-7b3d-4927-a733-a86e58c81a4d@gmail.com \
--to=prestwoj@gmail.com \
--cc=denkenz@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