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 09:39:44 -0800 [thread overview]
Message-ID: <545A60E0.8070308@candelatech.com> (raw)
In-Reply-To: <CAHqTa-21YOPiV_UxxWh23mB7AqLhj0n+h6eA5cTUH8eh32heRw@mail.gmail.com>
On 11/03/2014 05:35 PM, Avery Pennarun wrote:
> On Mon, Nov 3, 2014 at 8:04 PM, Ben Greear <greearb@candelatech.com> wrote:
>> If I am reading my results right, it takes over 2 seconds to associate an
>> ath10k station with WPA2 PSK on my systems.
>>
>> I was thinking this should be quite a bit faster than this...
>>
>> Has anyone done any similar measurements?
>
> I haven't noticed any delay like this. WPA2 PSK negotiation is on the
> order of ~200ms or less. Then DHCP screws around for a few seconds,
> often.
>
> A packet trace would probably be useful for narrowing it down :)
>
First part of my problem is that I had some extra debugging turned on and
that was being sent to serial console, which is slow.
But, even with that off I am still seeing ~200ms at best.
Ath9k system on crappy old Atom processors usually completes in
less than 20ms for comparison.
Off to go spelunking in the ath10k code :P
Thanks,
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
next prev parent reply other threads:[~2014-11-05 17:40 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 [this message]
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
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=545A60E0.8070308@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.