From: Johannes Berg <johannes@sipsolutions.net>
To: greearb@candelatech.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] mac80211: Optimize scans on current operating channel.
Date: Sun, 23 Jan 2011 10:18:13 +0100 [thread overview]
Message-ID: <1295774293.3639.15.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1295633142-7437-1-git-send-email-greearb@candelatech.com>
On Fri, 2011-01-21 at 10:05 -0800, greearb@candelatech.com wrote:
> + * @SCAN_LEFT_OPER_CHANNEL: Set this flag if the scan process leaves the
> + * operating channel at any time. If scanning ONLY the current operating
> + * channel this flag should not be set, and this will allow fewer
> + * offchannel changes.
Why does this make sense? In the code below, you do
> - ieee80211_hw_config(local, IEEE80211_CONF_CHANGE_CHANNEL);
> + if ((local->oper_channel != local->hw.conf.channel) || was_hw_scan)
> + ieee80211_hw_config(local, IEEE80211_CONF_CHANGE_CHANNEL);
> +
> if (!was_hw_scan) {
> ieee80211_configure_filter(local);
> drv_sw_scan_complete(local);
> - ieee80211_offchannel_return(local, true);
> + if (test_bit(SCAN_LEFT_OPER_CHANNEL, &local->scanning))
> + ieee80211_offchannel_return(local, true);
so you could just as well use a local variable (the first if you add is
exactly this test).
> static void ieee80211_scan_state_leave_oper_channel(struct ieee80211_local *local,
> unsigned long *next_delay)
> {
> + ieee80211_offchannel_stop_beaconing(local);
> +
Won't that confuse drivers that expect not to be beaconing between
sw_scan_start and sw_scan_end?
Also, are you sure the filter configuration works correctly this way? If
you can, I'd like to look at a binary trace of the commands going to the
device with this change: "trace-cmd record -e mac80211".
johannes
next prev parent reply other threads:[~2011-01-23 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 18:05 [PATCH v2] mac80211: Optimize scans on current operating channel greearb
2011-01-23 9:18 ` Johannes Berg [this message]
2011-01-23 15:49 ` Ben Greear
2011-01-24 22:12 ` Ben Greear
2011-01-26 15:22 ` Johannes Berg
2011-01-26 17:28 ` Ben Greear
2011-01-26 15:36 ` Johannes Berg
2011-01-26 18:10 ` Ben Greear
2011-01-27 13:56 ` Johannes Berg
2011-01-26 18:39 ` Ben Greear
2011-01-27 13:55 ` 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=1295774293.3639.15.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--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).