All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 9/9] mac80211: implement multi-interface CSA
Date: Mon, 20 Jan 2014 12:06:45 +0100	[thread overview]
Message-ID: <1390216005.4335.19.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQk62antiWbq7MxmjP_caj7xTOj699eiQO-TPFY32oX+5Q@mail.gmail.com> (sfid-20140116_113329_047866_CA32194F)

On Thu, 2014-01-16 at 11:33 +0100, Michal Kazior wrote:

> If you assume a driver supports multi-channel but isn't capable of
> multi-interface CSA you'll be running into timing issues. After you
> detect radar you have a limited time to quiesce. You might end up
> exceeding that limit if you move APs one-by-one.

That probably won't work anyway since you could probably not move them
one by one anyway due to channel context limitations.

> With my patches as they are new hostap will try sending new channel
> switch command but since it doesn't contain ifindex old kernel will
> respond with a -EINVAL and userspace has no way of knowing if the
> command was actually malformed or isn't supported. hostap could still,
> however, work in a best effort manner and fallback to the old command
> variant.

Well, you're looking at it reactively. I was more thinking hostapd might
want to look at it proactively and, for example, refuse setting up
multiple BSSes on a radar channel if multi-switch isn't supported. But
for that, it has to know upfront rather than realizing it reactively
when trying to switch.

johannes


  reply	other threads:[~2014-01-20 11:06 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
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 [this message]
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=1390216005.4335.19.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.