On Wed, 2013-06-05 at 10:10 +0200, Arend van Spriel wrote: > On 06/05/2013 09:46 AM, Johannes Berg wrote: > > On Tue, 2013-06-04 at 14:35 +0000, Malinen, Jouni wrote: > > > >> In general, I'd agree. However, I would like to get information of any > >> peer device being in active PBC mode. This would require either getting > >> those Probe Request frames > > > > I think I like that alternative better :-) > > > > I know I wouldn't find it quickly ... can you be more specific about > > what "being in active PBC mode" means? Is that easily detectable? > > > > I'm thinking we should just document this (and be as specific about it > > as we can) in the documentation for the offload feature. > > Remark from the sideline. One of the motivations for the P2P find > offload (when done on the device) is that the host can sleep, right? So > how/when does wpa_s want these Probe Request frames. After the > driver/device completed the find? I don't think the device can really _sleep_ during this time, but it allows reducing CPU wakeups. If you really wanted to sleep then you'd have to buffer at least some information and have some sort of wakeup trigger. That'll probably be done eventually, but it's not the rationale here I think. The way I see it, this patch allows being discoverable and discovering other peers with much less impact on CPU usage. The next step would be P2P-listen offload, which is more interesting for being discoverable, and should also have probe request offload similar to what we're discussing here. johannes -- 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
