From: Johannes Berg <johannes@sipsolutions.net>
To: "Coelho, Luciano" <luciano.coelho@intel.com>
Cc: Simon Wunderlich <sw@simonwunderlich.de>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC v2 2/2] mac80211: only set CSA beacon when at least one beacon must be transmitted
Date: Wed, 06 Nov 2013 13:36:33 +0100 [thread overview]
Message-ID: <1383741393.14307.43.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1383740486.4256.65.camel@porter.coelho.fi>
On Wed, 2013-11-06 at 12:22 +0000, Coelho, Luciano wrote:
> > Well even then - the question is who would ever want to use and test
> > count<=1?
>
> I guess the reason to have this is when you must evacuate the channel
> immediately, so you transmit the action frame and jump out. If your
> beacon interval is long (for whatever reason), waiting for the next TBTT
> to announce the CSA may take longer than the time required to stop
> transmitting.
Fair point, so I guess we'd want to also test that :)
johannes
prev parent reply other threads:[~2013-11-06 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 20:54 [RFC v2 1/2] mac80211: don't transmit beacon with CSA count 0 Luciano Coelho
2013-11-05 20:54 ` [RFC v2 2/2] mac80211: only set CSA beacon when at least one beacon must be transmitted Luciano Coelho
2013-11-06 10:51 ` Johannes Berg
2013-11-06 11:28 ` Coelho, Luciano
2013-11-06 11:31 ` Johannes Berg
2013-11-06 11:52 ` Coelho, Luciano
2013-11-06 12:06 ` Johannes Berg
2013-11-06 11:47 ` Simon Wunderlich
2013-11-06 12:03 ` Coelho, Luciano
2013-11-06 12:06 ` Johannes Berg
2013-11-06 12:22 ` Coelho, Luciano
2013-11-06 12:36 ` 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=1383741393.14307.43.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=sw@simonwunderlich.de \
/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