linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 26 Jan 2011 16:36:28 +0100	[thread overview]
Message-ID: <1296056188.3635.36.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:
> From: Ben Greear <greearb@candelatech.com>
> 
> This should decrease un-necessary flushes, on/off channel work,
> and channel changes in cases where the only scanned channel is
> the current operating channel.
> 
> Signed-off-by: Ben Greear <greearb@candelatech.com>
> ---
> 
> v2:  Check channels instead of flag when determining if we should
>   do a channel change in scan_completed_finish.

Can you look at work.c -- where we call
ieee80211_offchannel_stop_beaconing etc.

In this patch, you're moving the call to
ieee80211_offchannel_stop_beaconing next to
ieee80211_offchannel_stop_station in scan.c.

Therefore, you can combine those two into one function.

However, I guess it'd also be nice to also address the TODO in work.c
and move the "don't do so much if not really off-channel" logic into
that function? You must run into that when trying to associate on one
vif and the others get stopped etc. unnecessarily to do that.

johannes


  parent reply	other threads:[~2011-01-26 15:36 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
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 [this message]
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=1296056188.3635.36.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).