On 2013-02-25 11:25 AM, Johannes Berg wrote: > On Mon, 2013-02-25 at 06:54 +0100, Felix Fietkau wrote: > >> Most devices have some kind of connection manager that has a high-level >> perspective of when it's fully connected (which includes DHCP/bootp). >> Why not just let that connection manager set a sane maximum network >> latency value via pm_qos network_latency and derive btcoex weight >> changing and multi-channel settings from that? > > Frankly, I don't think that's going to work well. We tried using the > pm_qos framework once and nothing ever used it. Android isn't going to > change to it, so we'd be stuck with hacks like setting pm_qos in > wpa_supplicant which is just as awkward. If only the connection manager gets changed to use it, that would already be enough. It doesn't have to be pushed into dhcp clients and other applications. > Also, what you mostly want isn't really so much a weight but rather a > time-based approach to give it high priority until the connection > handshake completes (we already do for auth/assoc/... until authorized) > so I think using the pm_qos framework to give priority wouldn't work > very well since there'd also be no way to tell when it was "done" Just release the latency requirement in the connection manager once the handshake is done. It knows... - Felix -- 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
