> It might even be beneficial to cancel a currently active > background scan once the TX queue is filling up and report the > already gathered information to the user space. This brings policy into the kernel. Why should TX data be more important than a scan result? If an app only gets partial scan results because of "too much tx data", what can the app do against it? Nothing. It can just retrigger a scan again. But what if then there is still "too much tx data"? Then the times of n * "partial scan" might be bigger than a "real scan" and a happy application. -- 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
