On 10/18/2012 08:44 PM, Bing Zhao wrote:
Hi Arend,
From: Sam Leffler <sleffler@xxxxxxxxxxxx>
Add NL80211_SCAN_FLAG_LOW_PRIORITY flag support. It tells drivers
that this is a low priority scan request, so that they can take
necessary action.
Drivers need to advertise low priority scan capability during
registration.
I missed the previous versions of this patch series, but what 'necessary
action' is needed for a low priority scan request. Patch #6 gives a clue
so my assumption is that a low prio scan will be *aborted* when
associated and data traffic is available. Is that correct? Could it also
It's up to the driver to decide and implement the 'low priority scan' feature.
The driver can defer or abort the low priority scan request depending on various conditions.
For example, when heavy data traffic is on going you may want to abort the scan.
Thanks, Bing
I always find such answer tricky. Seeing where this is coming from I
suspect there is some high-level expectation from user-space
perspective. I suspect it is something like: A low-prio scan should not
affect a data transfer (iperf, nfs i/o, etc.) noticably.
Thanks for collecting the reading material ;-)
Gr. AvS
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
