linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>, Jouni Malinen <j@w1.fi>,
	Paul Stewart <pstew@google.com>,
	Amod Bodas <Amod.Bodas@Atheros.com>,
	Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>
Subject: Re: [PATCH v2 2/3] mac80211: wait until completely disassociated before new association
Date: Tue, 05 Oct 2010 09:59:42 +0200	[thread overview]
Message-ID: <1286265582.3641.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20101004205551.GR2105@tux>

On Mon, 2010-10-04 at 13:55 -0700, Luis R. Rodriguez wrote:

> > We don't need to go out of PS state to just TX, but we'd need to be
> > careful to TX with asleep bit.
> 
> I got what you meant here.
> 
> > That said, we don't TX data frames then.
> 
> But not here. Right now I am going to assume that we actually are
> transmitting some frames for the delba when we try to tear down
> the BA agreements with the old AP and the new AP are on the
> same band, we just likely transmit it on the wrong channel.

Yes, but delBA aren't data frames. The queue stop etc. doesn't pertain
to them.

> Ah and also we did call ieee80211_offchannel_stop_beaconing() prior
> to processing work_work stuff so that should take care of stopping
> beaconing but that also turns off all TX queues... so yeah you're
> right. The race here was just within work items assuming they can
> transmit on other channels than the wk->chan.

Did any work item actually assume that? Except maybe for your patch 1 in
this set?

> > > Also this seems buggy, we do not take into consideration how much offchannel
> > > work we are doing in consideration against the current AP's DTIM interval as
> > > we do when going offchannel for scan work. We should merge that code for
> > > this offchannel work_work loop.
> > 
> > True, we don't do _any_ timing here.
> 
> We can resolve that later, I'll add that to the TODO list.

Come to think of it -- some p2p stuff in the supplicant might time out
if we do this, I think we need to cut the drivers/mac80211 some more
slack in the supplicant and not assume the remain-on-channel will start
quickly.

johannes


  reply	other threads:[~2010-10-05  7:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 20:33 [PATCH v2 0/3] mac80211: fix rate_control_send_low warnings for delbas Luis R. Rodriguez
2010-10-01 20:33 ` [PATCH v2 1/3] mac80211: fix channel assumption for association done work Luis R. Rodriguez
2010-10-04 13:12   ` Johannes Berg
2010-10-01 20:33 ` [PATCH v2 2/3] mac80211: wait until completely disassociated before new association Luis R. Rodriguez
2010-10-04 13:14   ` Johannes Berg
2010-10-04 16:36     ` Luis R. Rodriguez
2010-10-04 16:39       ` Johannes Berg
2010-10-04 18:04         ` Luis R. Rodriguez
2010-10-04 18:44           ` Johannes Berg
2010-10-04 20:55             ` Luis R. Rodriguez
2010-10-05  7:59               ` Johannes Berg [this message]
2010-10-05 19:36                 ` Luis R. Rodriguez
2010-10-05 19:43                   ` Johannes Berg
2010-10-01 20:33 ` [PATCH v2 3/3] mac80211: move to the home channel for disassociation when roaming Luis R. Rodriguez
2010-10-04 13:15   ` Johannes Berg
2010-10-04 16:38     ` Luis R. Rodriguez
2010-10-04 16:41       ` Johannes Berg
2010-10-04 17:23         ` Luis R. Rodriguez
2010-10-04 18:39           ` Johannes Berg
2010-10-04 21:03             ` Luis R. Rodriguez
2010-10-01 20:50 ` [PATCH v2 0/3] mac80211: fix rate_control_send_low warnings for delbas Luis R. Rodriguez
2010-10-04 13:27 ` Johannes Berg
2010-10-04 16:41   ` Luis R. Rodriguez
2010-10-04 16:42     ` Johannes Berg
2010-10-04 17:25       ` Luis R. Rodriguez
2010-10-04 17:30         ` Johannes Berg
2010-10-04 17:35           ` Luis R. Rodriguez
2010-10-04 18:39             ` Johannes Berg
2010-10-04 20:39             ` Jouni Malinen
2010-10-04 21:07               ` Luis R. Rodriguez
2010-10-04 22:47                 ` Jouni Malinen
2010-10-04 23:50                   ` Luis R. Rodriguez
2010-10-05  7:57                     ` Johannes Berg
2010-10-05 17:03                       ` Luis R. Rodriguez

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=1286265582.3641.6.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=Amod.Bodas@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Vasanth.Thiagarajan@Atheros.com \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=pstew@google.com \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).