All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Slow connect times?
Date: Wed, 05 Nov 2014 16:49:25 -0800	[thread overview]
Message-ID: <545AC595.1020608@candelatech.com> (raw)
In-Reply-To: <CAHqTa-0nHBHR5FrxWvDfp7bhfN8LOK-EhpX+LDYPwBRvkZSWxw@mail.gmail.com>

On 11/05/2014 11:12 AM, Avery Pennarun wrote:
> On Wed, Nov 5, 2014 at 11:03 AM, Ben Greear <greearb@candelatech.com> wrote:
>> Does not appear to be an AP problem, as ath9k stations to the ath10k AP are all
>> in the 20ms range.
> 
> Ah, ok, I just assumed you were using ath10k as an AP.  In that case I
> know nothing :)
> 


Ahhh, found the problem.  Firmware was trying to be helpful and
reserve the channel on vdev-start.  But, took it 200+ms to grab the
reservation when another vdev exists, and it shouldn't be needed
anyway as far as I can tell.

Disabled that 'feature' by hacking on driver a bit to pass a new flag to modified firmware
to tell it to ignore the reservation logic, and now a second station vdev associates
in about 6-8 ms :)

Take it easy,
Ben

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


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      reply	other threads:[~2014-11-06  0:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  1:04 Slow connect times? Ben Greear
2014-11-04  1:35 ` Avery Pennarun
2014-11-04  2:45   ` Ben Greear
2014-11-05 17:39   ` Ben Greear
2014-11-05 18:58     ` Avery Pennarun
2014-11-05 19:03       ` Ben Greear
2014-11-05 19:12         ` Avery Pennarun
2014-11-06  0:49           ` Ben Greear [this message]

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=545AC595.1020608@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=apenwarr@gmail.com \
    --cc=ath10k@lists.infradead.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.