public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Lars Ericsson <Lars_Ericsson@telia.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Slow roaming in mac80211 (2.6.30).
Date: Wed, 22 Jul 2009 00:30:54 +0200	[thread overview]
Message-ID: <1248215454.11735.24.camel@johannes.local> (raw)
In-Reply-To: <1B3FCF72EBBC44A39F5A80B8FFBF6402@gotws1589>

[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]

Lars,

> A first analysis gives that the two delays are the ieee80211_sta_work()
> timeout.  There are many events trigging ieee80211_sta_work(), but
> since only the timer sets IEEE80211_STA_REQ_RUN, nothing will happen.

TBH I really no longer know the 2.6.30 code well, so I don't know.

> Questions; 
> - Why does mac80211 tells the wpa_supplicant that the AP
> is gone (87.632965), and then blocks/delays the actions taken by the
> wpa_supplicant?  

The real question is: why the hell is it probing the AP?

> [   87.632965] wlan0: deauthenticated (Reason: 1)
> [   87.733979] [B] LaE: SCANRQUEST: SSID=AGV
> [   88.629931] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 1
> [   88.829932] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 2
> [   89.029944] wlan0: direct probe to AP 00:40:96:a0:e7:e7 try 3
> [   89.230016] wlan0: direct probe to AP 00:40:96:a0:e7:e7 timed out

It doesn't really block actions, but it delays the scan because it's
busy doing the probing. So only after the probing fails will it start
the scan, and complete it within about 1.4 seconds.

> - Why are some wpa_supplicant actions (90.702325)
> not event driven?
> 
> It looks to me as if we have to decision makers here. For me the
> wpa_supplicant is the one that make the decision. Once the mac80211
> gives up and feedback that the AP is gone, it should just sit 
> and wait for next decision from the wpa_supplicant.

I agree -- the spurious probing is strange. But I also have to admit
that basically I don't care as long as it works -- most of this is just
a side effect of how wireless extensions work.

> I had a few patches for this for .26, but since the code is changed
> they do not apply. Before I create new patches I would like to get
> your opinion on this.

I would suggest you just use wpa_supplicant -Dnl80211, which should help
a lot with this kind of things.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-07-21 22:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 21:21 Slow roaming in mac80211 (2.6.30) Lars Ericsson
2009-07-21 22:30 ` Johannes Berg [this message]
2009-07-23  9:40   ` Lars Ericsson
2009-07-23  9:54     ` Johannes Berg
2009-07-22  8:18 ` Lam Yoke Khei
2009-07-22  8:55 ` Holger Schurig

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=1248215454.11735.24.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=Lars_Ericsson@telia.com \
    --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