From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Malinen, Jouni" <jouni@qca.qualcomm.com>,
qca_vkondrat <qca_vkondrat@qca.qualcomm.com>,
"Peer, Ilan" <ilan.peer@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Rodriguez, Luis" <rodrigue@qca.qualcomm.com>,
"John W . Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v8] cfg80211: P2P find phase offload
Date: Wed, 5 Jun 2013 10:38:12 +0200 [thread overview]
Message-ID: <51AEF8F4.2020809@broadcom.com> (raw)
In-Reply-To: <1370420283.8920.21.camel@jlt4.sipsolutions.net>
On 06/05/2013 10:18 AM, Johannes Berg wrote:
> 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.
Right. Indeed meant CPU wakeups.
> 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.
Ah, I thought that was included. The WFA spec is a bit confusing using
terms 'phases' and 'states'. There is a SCAN phase and a FIND phase.
During the FIND phase a device can be in SEARCH or LISTEN state. I know
it is all terminology, but I was confused. At least the commit message
seems to imply both states are offloaded.
Regards,
Arend
next prev parent reply other threads:[~2013-06-05 8:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 6:44 [PATCH v8] P2P find phase offload Vladimir Kondratiev
2013-06-04 6:44 ` [PATCH v8] cfg80211: " Vladimir Kondratiev
2013-06-04 10:07 ` Peer, Ilan
2013-06-04 11:24 ` Vladimir Kondratiev
2013-06-04 12:07 ` Johannes Berg
2013-06-04 14:03 ` Vladimir Kondratiev
2013-06-04 14:29 ` Johannes Berg
2013-06-04 14:35 ` Malinen, Jouni
2013-06-04 16:47 ` Vladimir Kondratiev
2013-06-04 18:30 ` Jouni Malinen
2013-06-05 7:10 ` Vladimir Kondratiev
2013-06-05 7:53 ` Johannes Berg
2013-06-05 13:30 ` Vladimir Kondratiev
2013-06-11 12:12 ` Johannes Berg
2013-06-05 7:46 ` Johannes Berg
2013-06-05 8:10 ` Arend van Spriel
2013-06-05 8:18 ` Johannes Berg
2013-06-05 8:38 ` Arend van Spriel [this message]
2013-06-05 16:26 ` Vladimir Kondratiev
2013-06-05 8:12 ` Jouni Malinen
2013-06-04 12:10 ` Peer, Ilan
2013-06-04 10:43 ` Johannes Berg
2013-06-04 6:51 ` [PATCH v8] " Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51AEF8F4.2020809@broadcom.com \
--to=arend@broadcom.com \
--cc=ilan.peer@intel.com \
--cc=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox