From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] mac80211: Allow scanning single channel if other VIF is associated.
Date: Wed, 29 Sep 2010 09:58:54 -0700 [thread overview]
Message-ID: <4CA3704E.1070702@candelatech.com> (raw)
In-Reply-To: <1285778901.3756.25.camel@jlt3.sipsolutions.net>
On 09/29/2010 09:48 AM, Johannes Berg wrote:
> On Wed, 2010-09-29 at 08:30 -0700, Ben Greear wrote:
>
>> Does this portion seem useful as a stand-alone patch? It does not
>> depend on the other scan-one logic.
>
> Somewhat, but it seems a bit buggy?
>
>> diff --git a/net/mac80211/work.c b/net/mac80211/work.c
>> index ae344d1..1bfc1e0 100644
>> --- a/net/mac80211/work.c
>> +++ b/net/mac80211/work.c
>> @@ -910,12 +910,17 @@ static void ieee80211_work_work(struct work_struct *work)
>> * happen to be on the same channel as
>> * the requested channel
>> */
>> - ieee80211_offchannel_stop_beaconing(local);
>> - ieee80211_offchannel_stop_station(local);
>> -
>> - local->tmp_channel = wk->chan;
>> - local->tmp_channel_type = wk->chan_type;
>> - ieee80211_hw_config(local, 0);
>> + if (!(wk->chan == local->scan_channel ||
>> + (wk->chan == local->oper_channel&&
>
> I don't think work items will ever run while scanning? And also, this
> might need to check the channel type as well, which isn't quite
> necessary right now (since no works requires HT channels) but would seem
> cleaner.
Just in case work ever does happen when scanning, I think we should
leave this check in.
I'll add a check for channel_type being the same as well.
>> + !local->scan_channel))) {
>> + /* Only change channels if we need to */
>> + ieee80211_offchannel_stop_beaconing(local);
>> + ieee80211_offchannel_stop_station(local);
>> +
>> + local->tmp_channel = wk->chan;
>> + local->tmp_channel_type = wk->chan_type;
>> + ieee80211_hw_config(local, 0);
>> + }
>> started = true;
>> wk->timeout = jiffies;
>
> Also, I believe it needs matching code to not do all the return stuff
> since we never left the channel, and I think it still needs to set
> tmp_channel so that nothing will switch away underneath or so... not
> quite sure.
Ok, that sounds good. I'll work on a revised patch when I get a chance.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-29 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 21:17 [PATCH v3] mac80211: Allow scanning single channel if other VIF is associated greearb
2010-09-29 7:02 ` Johannes Berg
2010-09-29 15:30 ` Ben Greear
2010-09-29 16:48 ` Johannes Berg
2010-09-29 16:58 ` Ben Greear [this message]
2010-09-29 17:03 ` Johannes Berg
2010-09-29 17:44 ` Ben Greear
2010-09-29 18:05 ` 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=4CA3704E.1070702@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).