<div class="gmail_quote">On Sun, Nov 29, 2009 at 3:37 PM, Dan Williams <span dir="ltr"><<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It's pretty pointless to trigger a new scan when a control interface<br>
calls SELECT_NETWORK if the scan results are less than 10 seconds old.<br>
This speeds up associations when the connection manager has already<br>
requested a scan to determine what BSS to connect to, and then tells the<br>
supplicant to select that BSS, which previously would trigger yet<br>
another scan a few seconds after the first one.<br>
<br></blockquote><div><br></div><div>It's difficult for me to tell from the patch but in my experience you want to treat the scan results as a cache and age entries out and/or flush explicitly under certain conditions. This appears to be something short of that.</div>
<div><br></div><div>There's also the issue that this process may already take place below wpa_supplicant in which case you don't want it doing the same work.</div><div><br></div><div>Related to this whole issue is that the d-bus api needs to provide better control over scanning and likely also split out scanning from MLME operations like associate.</div>
<div><br></div><div>-Sam</div><div> </div></div>