From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 6/9] mac80211: track CSA globally
Date: Wed, 15 Jan 2014 15:21:08 +0100 [thread overview]
Message-ID: <1389795668.4338.20.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQkbd8UtGz3DwiL8aKDHAuVob3KZ_MYjEVmy1TeGKYB-oQ@mail.gmail.com> (sfid-20140115_151120_804532_1E6AD0CD)
On Wed, 2014-01-15 at 15:11 +0100, Michal Kazior wrote:
> >> >> For CSA to be safe it needs to be treated the same
> >> >> way as radar detection, scanning and remain on
> >> >> channel - all of those (including CSA) must be
> >> >> mutually exclusive.
> >> >
> >> > This I don't understand. Why couldn't you do a remain-on(some
> >> > other)-channel or scan while counting down the beacons?
> >>
> >> My concern is software offchannel (be it scan or roc) involves channel
> >> context switches. I wanted to avoid any channel context mangling while
> >> CSA is in progress. Does that make sense to you?
> >
> > No, I don't really get it. Why?
>
> Hmm. Perhaps I was a little overcautious. Offchannel stuff doesn't use
> channel contexts at all, right? It recalculates channel in hw_config()
> and doesn't touch channel contexts so it should be safe.
Software offchannel and scan are incompatible with channel contexts,
yes.
johannes
next prev parent reply other threads:[~2014-01-15 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:04 [RFC 0/9] mac80211: multi-interface CSA Michal Kazior
2014-01-15 12:04 ` [RFC 1/9] mac80211: fix possible memory leak on AP CSA failure Michal Kazior
2014-01-15 12:04 ` [RFC 2/9] mac80211: treat IBSS CSA finish failure seriously Michal Kazior
2014-01-15 13:07 ` Luca Coelho
2014-01-15 12:04 ` [RFC 3/9] mac80211: move csa_active setting in STA CSA Michal Kazior
2014-01-15 13:17 ` Johannes Berg
2014-01-15 12:04 ` [RFC 4/9] mac80211: fix sdata->radar_required locking Michal Kazior
2014-01-15 12:04 ` [RFC 5/9] mac80211: improve CSA locking Michal Kazior
2014-01-15 12:04 ` [RFC 6/9] mac80211: track CSA globally Michal Kazior
2014-01-15 13:19 ` Johannes Berg
2014-01-15 13:28 ` Michal Kazior
2014-01-15 13:29 ` Johannes Berg
2014-01-15 14:11 ` Michal Kazior
2014-01-15 14:21 ` Johannes Berg [this message]
2014-01-15 12:04 ` [RFC 7/9] Revert "cfg80211: disable CSA for all drivers" Michal Kazior
2014-01-15 12:04 ` [RFC 8/9] ath9k: prepare for multi-interface CSA support Michal Kazior
2014-01-15 12:04 ` [RFC 9/9] mac80211: implement multi-interface CSA Michal Kazior
2014-01-15 13:22 ` Johannes Berg
2014-01-16 9:28 ` Michal Kazior
2014-01-16 9:31 ` Johannes Berg
2014-01-16 10:33 ` Michal Kazior
2014-01-20 11:06 ` Johannes Berg
2014-01-16 11:04 ` Eliad Peller
2014-01-16 11:41 ` Michal Kazior
2014-01-15 13:21 ` [RFC 0/9] mac80211: " Johannes Berg
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=1389795668.4338.20.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).