From: Helmut Schaa <helmut.schaa@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Paul Stewart <pstew@google.com>,
"linux-wireless" <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org, Matt Smith <Matt.Smith@atheros.com>,
Srinivasa Duvvuri <Srinivasa.Duvvuri@atheros.com>,
Carolyn Waller <Carolyn.Waller@atheros.com>,
Amod Bodas <Amod.Bodas@atheros.com>,
David Quan <David.Quan@atheros.com>,
Bennyam Malavazi <Bennyam.Malavazi@atheros.com>,
Cliff Holden <Cliff.Holden@atheros.com>,
Aeolus Yang <Aeolus.Yang@atheros.com>,
Kevin Hayes <kevin@atheros.com>
Subject: Re: Roaming / offchannel enhancements for broadcast / multicast frames
Date: Sat, 9 Oct 2010 09:33:12 +0200 [thread overview]
Message-ID: <201010090933.13008.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <AANLkTimBXC9P7pf+-szK3A5FoS2Sjndr8AB9JR=7V-Sr@mail.gmail.com>
Am Samstag 09 Oktober 2010 schrieb Luis R. Rodriguez:
> > There's an additional issue about what happens
> > when we are in the middle of a bgscan and new tx traffic appears.
>
> We can force going back on channel in this case I think.
This already happens (scan.c):
523 if (associated && ( !tx_empty || bad_latency ||
524 listen_int_exceeded))
525 local->next_scan_state = SCAN_ENTER_OPER_CHANNEL;
526 else
527 local->next_scan_state = SCAN_SET_CHANNEL;
When the currently scanned channel is finished and tx traffic arrived
mac80211 will switch back to the operating channel. However, this doesn't
immediately switch back but waits for the channel scan to be completed.
next prev parent reply other threads:[~2010-10-09 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 19:54 Roaming / offchannel enhancements for broadcast / multicast frames Luis R. Rodriguez
2010-10-09 0:08 ` Paul Stewart
2010-10-09 0:43 ` Luis R. Rodriguez
2010-10-09 7:33 ` Helmut Schaa [this message]
2010-10-09 12:53 ` Johannes Berg
2010-10-11 22:28 ` Paul Stewart
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=201010090933.13008.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=Aeolus.Yang@atheros.com \
--cc=Amod.Bodas@atheros.com \
--cc=Bennyam.Malavazi@atheros.com \
--cc=Carolyn.Waller@atheros.com \
--cc=Cliff.Holden@atheros.com \
--cc=David.Quan@atheros.com \
--cc=Matt.Smith@atheros.com \
--cc=Srinivasa.Duvvuri@atheros.com \
--cc=kevin@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=pstew@google.com \
/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).