From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail2.candelatech.com ([208.74.158.173]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1Xm4Yy-0003qq-8e for ath10k@lists.infradead.org; Wed, 05 Nov 2014 17:40:09 +0000 Message-ID: <545A60E0.8070308@candelatech.com> Date: Wed, 05 Nov 2014 09:39:44 -0800 From: Ben Greear MIME-Version: 1.0 Subject: Re: Slow connect times? References: <5458261C.2020700@candelatech.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Avery Pennarun Cc: ath10k On 11/03/2014 05:35 PM, Avery Pennarun wrote: > On Mon, Nov 3, 2014 at 8:04 PM, Ben Greear 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 Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k