linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211_hwsim: notify user-space about channel change.
Date: Tue, 31 Mar 2015 08:56:38 -0700	[thread overview]
Message-ID: <551AC3B6.1040001@candelatech.com> (raw)
In-Reply-To: <1427812067.2057.27.camel@sipsolutions.net>

On 03/31/2015 07:27 AM, Johannes Berg wrote:
> On Wed, 2015-03-11 at 14:05 -0700, Ben Greear wrote:
> 
>> I took a look at the hw-scan code a bit...I guess we might could do additional
>> info calls to user-space as we iterate through the channels while scanning?
>>
>> A real driver would be causing the NIC to change channels at these junctures,
>> either by directly setting registers or sending some message off to the
>> target NIC's cpu, right?
> 
> Well, depends. Our driver just asks the firmware to do the scan, and it
> will do all the scheduling by itself, i.e. it'll go through the channels
> at convenient times etc.

I do not want to offload scanning in user-space, which is the equivalent
of what your driver is doing as far as the kernel is concerned?  If someone wants
to do that in the future, then sure, they can implement such a thing.

>> I would assume that off-channel work could do similar logic.
> 
> Yeah.
> 
>> Is that the sort of thing you had in mind?
> 
> To be honest, I'm not really sure myself. It seems to really do this
> you'd also need powersave handling (tell the AP you're going to sleep
> when scanning) and potentially P2P-GO NoA handling (tell the clients
> you're going to sleep).

Yes, I have plans to do that sort of thing..but I have not looked into
it properly yet.  Either way, it seems a bit orthogonal to changing
the channel..like first we send the PS packets, then change channel,
etc.


> The thing with hwsim right now is that it totally makes use of its
> ability to be on as many channels at the same time as it wants, so it
> doesn't have to worry about that, but if you want to actually have the
> channel "changed" then we need to handle a lot more details.

One step at a time I think...my patch should not break anything..userspace
that doesn't care can simply ignore the new message.

Thanks,
Ben

> 
> johannes
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2015-03-31 15:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 23:59 [RFC] mac80211_hwsim: notify user-space about channel change greearb
2015-02-23 11:49 ` Johannes Berg
2015-02-23 17:43   ` Ben Greear
2015-02-24 10:11     ` Johannes Berg
2015-02-24 14:36       ` Ben Greear
2015-02-24 14:40         ` Johannes Berg
2015-03-11 21:05           ` Ben Greear
2015-03-31 14:27             ` Johannes Berg
2015-03-31 15:56               ` Ben Greear [this message]
2015-04-14  8:13                 ` Johannes Berg
2015-04-14 14:56                   ` Ben Greear
2015-04-14 15:06                     ` Johannes Berg
2015-04-14 15:55                       ` Ben Greear
2015-04-15  9:33                         ` Johannes Berg
2015-04-15 15:06                           ` Ben Greear
2015-04-17 11:25                             ` 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=551AC3B6.1040001@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).