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 <linux-wireless@vger.kernel.org>
Subject: Re: [RFT/FYI] mac80211: revert on-channel work optimisations
Date: Fri, 17 Feb 2012 08:13:25 -0800	[thread overview]
Message-ID: <4F3E7CA5.7010207@candelatech.com> (raw)
In-Reply-To: <1329493491.3786.6.camel@jlt3.sipsolutions.net>

On 02/17/2012 07:44 AM, Johannes Berg wrote:
> On Tue, 2011-11-08 at 09:17 -0800, Ben Greear wrote:
>> On 11/08/2011 09:10 AM, Johannes Berg wrote:
>>> FYI -- I'm going to test this a bit more but I am going to put it in.
>>> The code is a mess -- look at how much code I remove below (and that's
>>> after everybody elses cleanups!) for a dubious optimisation.
>>>
>>> I agree that we should address this and we need to really do this to not
>>> mess up our aggregation state, but the current code is too complex and
>>> causing too many issues. We also need to think about this in the context
>>> of multi-virtual-channel support.
>>
>> Well crap.  Why don't you try to fix it right instead?
>>
>> I'll probably end up carrying this in my own tree so
>> that multiple vifs work well and don't constantly
>> reset the ath9k causing it to shit itself...
>
> 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?

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?

Thanks,
Ben


>
> johannes


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

  reply	other threads:[~2012-02-17 16:13 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 [this message]
2012-02-17 18:19       ` Johannes Berg
2012-02-17 18:38         ` Ben Greear
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=4F3E7CA5.7010207@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).