From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v3] mac80211: Optimize scans on current operating channel.
Date: Mon, 31 Jan 2011 18:32:33 +0100 [thread overview]
Message-ID: <1296495153.3812.34.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D46F1B4.1020504@candelatech.com>
On Mon, 2011-01-31 at 09:30 -0800, Ben Greear wrote:
> > Well, sort of no, and sort of yes -- both will disrupt that code in a
> > sense, but even scanning on the same channel will disrupt it due to the
> > beacon diversion, unless we copy the beacons and give them to both sides
> > (scan and mlme)?
>
> Seems to me both sides should get them. I'll try to figure out how to
> do that properly today.
>
> But, if work_work() takes us off-channel often enough, wouldn't that
> cause undue beacon loss and/or timed-out tx acks?
Not TX ACKs really -- the device shouldn't be switching inbetween, but
beacon loss yeah.
> Are there any guarantees
> about how often and how long work_work() can take us off-channel?
No, with p2p it can be quite a bit of time.
johannes
prev parent reply other threads:[~2011-01-31 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 20:37 [RFC v3] mac80211: Optimize scans on current operating channel greearb
2011-01-27 13:52 ` Johannes Berg
2011-01-27 17:17 ` Ben Greear
2011-01-28 13:24 ` Johannes Berg
2011-01-28 18:47 ` Ben Greear
2011-01-27 18:33 ` Ben Greear
2011-01-28 13:20 ` Johannes Berg
2011-01-28 19:22 ` Ben Greear
2011-01-31 13:56 ` Johannes Berg
2011-01-31 17:30 ` Ben Greear
2011-01-31 17:32 ` Johannes Berg [this message]
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=1296495153.3812.34.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.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;
as well as URLs for NNTP newsgroup(s).