Skip to contentSkip to conversation

Slow connect times?

DISCUSSION Ben Greear 2 participants 8 messages Nov 4, 2014 – Nov 6, 2014 Qualcomm Atheros ATH10K wireless driver

lore
Share & tools
lore

Ben Greear

author
#0 lore raw

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?

Thanks,
Ben

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#1 lore raw
Quoted 6 lines · Ben Greear

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 :)

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#2 lore raw
Quoted 6 lines · Avery Pennarun
Quoted 5 lines · Ben Greear

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...

Quoted 7 lines
Quoted 1 line

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 :)

Could be something weird with my setup. I'll dig into it some more sometime soon.

Thanks,
Ben

Signature · 7 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
author
#3 lore raw
In reply to Avery Pennarun
Quoted 6 lines · Avery Pennarun
Quoted 5 lines · Ben Greear

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...

Quoted 8 lines
Quoted 1 line

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

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
#4 lore raw
Quoted 18 lines · Ben Greear
Quoted 6 lines · Avery Pennarun
Quoted 5 lines · Ben Greear

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...

Quoted 7 lines
Quoted 1 line

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.

Quoted 6 lines

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

That's very interesting for me. 200ms was kind of a worst case in my traces, and I'm mostly seeing 20-40ms. I think the key exchange is all hostapd, so I'm surprised it would take so long. Do you have a trace?

Note that I *have* seen weird problems with delayed probe packets to some clients, which could cause things like this. But that's apparently only because I applied Michal's patch to get rid of queue blocking :)

_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k

author
#5 lore raw
Quoted 31 lines · Avery Pennarun
Quoted 18 lines · Ben Greear
Quoted 6 lines · Avery Pennarun
Quoted 5 lines · Ben Greear

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...

Quoted 7 lines
Quoted 1 line

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.

Quoted 6 lines

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

That's very interesting for me. 200ms was kind of a worst case in my traces, and I'm mostly seeing 20-40ms. I think the key exchange is all hostapd, so I'm surprised it would take so long. Do you have a trace?

Quoted 5 lines

Note that I *have* seen weird problems with delayed probe packets to some clients, which could cause things like this. But that's apparently only because I applied Michal's patch to get rid of queue blocking :)

My first station comes up in ~20ms, the second one (on same machine) takes ~200ms. If I try bringing up 10 as fast as supplicant can do it's thing, then it takes around 1 sec for each station.

Does not appear to be an AP problem, as ath9k stations to the ath10k AP are all in the 20ms range.

I'm updating my test systems Fedora 20 to have easier use of some debugging tools and will then start figuring out where the slowness is. I'm running my firmware with patches that should help with flush related problems, but that is still my first suspect!

Thanks,
Ben

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k
author
#7 lore raw
Quoted 7 lines · Avery Pennarun
Quoted 2 lines · Ben Greear

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

Signature · 8 lines
Ben Greear <[email protected]>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/ath10k