From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT/FYI] mac80211: revert on-channel work optimisations
Date: Fri, 17 Feb 2012 10:38:54 -0800 [thread overview]
Message-ID: <4F3E9EBE.60602@candelatech.com> (raw)
In-Reply-To: <1329502761.3330.0.camel@jlt3.sipsolutions.net>
On 02/17/2012 10:19 AM, Johannes Berg wrote:
> On Fri, 2012-02-17 at 08:13 -0800, Ben Greear wrote:
>
>>> Given the auth/assoc redesign that went in now, are you still carrying
>>> this? Does the redesign address your problem?
>>
>> I haven't looked yet...still stuck back on 3.0 kernel for the
>> most part.
>>
>> I should be moving to 3.3 sometime soon, and will see how it works.
>>
>> I was thinking that I would ignore the work logic for now and probably
>> just focus on re-applying the on-channel scan optimization first.
>>
>> Are you done, or mostly done with the re-architecture you were working on?
>
> Yes, I'm done.
>
>> I know you didn't like the scan optimization from before...do you have any
>> ideas on how it might be done more to your liking?
>
> I, umm, don't even remember what that was about :)
The basic idea is that if the user requests that we only
scan a single channel, and that channel is the operating channel,
we should be able to scan without interrupting any other
packet transmission/reception, and without kicking the NIC to make it go off/on
channel, etc.
Basically I had to complicate the scan state machine
in order to minimize going off-channel (if indeed we are only
scanning one current channel).
I'd want to re-add the logic that let us receive pkts while
scanning (so long as we are scanning on the oper-channel)
as well.
Might be a while before I can get back to this, but I'll
let you know when I get started if no one beats me to it.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-02-17 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 17:10 [RFT/FYI] mac80211: revert on-channel work optimisations Johannes Berg
2011-11-08 17:17 ` Ben Greear
2011-11-08 17:18 ` Johannes Berg
2011-11-08 17:25 ` Ben Greear
2011-11-08 17:56 ` Johannes Berg
2011-11-08 18:08 ` Ben Greear
2011-11-08 18:38 ` Johannes Berg
2011-11-25 11:27 ` Stanislaw Gruszka
2011-11-25 11:29 ` Johannes Berg
2012-02-17 15:44 ` Johannes Berg
2012-02-17 16:13 ` Ben Greear
2012-02-17 18:19 ` Johannes Berg
2012-02-17 18:38 ` Ben Greear [this message]
2012-02-18 17:39 ` Stanislaw Gruszka
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=4F3E9EBE.60602@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.