Return-path: Received: from mail-bk0-f45.google.com ([209.85.214.45]:54308 "EHLO mail-bk0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751838AbaAON2P convert rfc822-to-8bit (ORCPT ); Wed, 15 Jan 2014 08:28:15 -0500 Received: by mail-bk0-f45.google.com with SMTP id v16so699444bkz.32 for ; Wed, 15 Jan 2014 05:28:14 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1389791963.4338.4.camel@jlt4.sipsolutions.net> References: <1389787494-7361-1-git-send-email-michal.kazior@tieto.com> <1389787494-7361-7-git-send-email-michal.kazior@tieto.com> <1389791963.4338.4.camel@jlt4.sipsolutions.net> Date: Wed, 15 Jan 2014 14:28:14 +0100 Message-ID: (sfid-20140115_142825_378123_6E8519E1) Subject: Re: [RFC 6/9] mac80211: track CSA globally From: Michal Kazior To: Johannes Berg Cc: linux-wireless Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 15 January 2014 14:19, Johannes Berg wrote: > On Wed, 2014-01-15 at 13:04 +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? Michał