From: Johannes Berg <johannes@sipsolutions.net>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Karl Beldan <karl.beldan@rivierawaves.com>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Andrei Otcheretianski <andrei.otcheretianski@intel.com>
Subject: Re: [PATCH v4] mac80211_hwsim: claim CSA support for AP
Date: Mon, 16 Dec 2013 13:51:54 +0100 [thread overview]
Message-ID: <1387198314.4665.27.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20131205172627.GA3593@magnum.frso.rivierawaves.com> (sfid-20131205_182708_985437_520E9348)
On Thu, 2013-12-05 at 18:26 +0100, Karl Beldan wrote:
> > Overall it seems ok, but all the purpose of csa_finished is not very
> > clear..
> > It looks that this patch tries to avoid extra beaconing on the previous
> > channel/hitting the warning..
> Yes, it avoids extra beacons.
>
> > But the problem is much bigger here, it means that we didn't switch in
> > time (before the next beacon) so it's ok to hit the warning here and
> > transmit extra beacon with count==1.
> Precisely what I discussed in the previous emails.
> However, I'd expect WARN*s to trigger on unexpected conditions .. though
> I haven't seen any warning, the codepath nearly seems to beg for it.
>
> > So if we see a lot of such warnings, maybe we need to fix
> > ieee80211_csa_finish instead (not using work for example)
> The replies I got from the race I detailed felt like ppl wanted to
> prevent this in-driver, now we agree this race prone work is a flaw.
> Maybe I'll send a v5 for hwsim relying on future in-stack improvement to
> avoid extra beacon instead of doing this in-driver, with some
> appropriate comments.
Generally, I think I'd prefer simpler code in the driver(s) over simpler
code in the stack, since the former tends to get duplicated a lot.
johannes
next prev parent reply other threads:[~2013-12-16 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 16:38 [PATCH v4] mac80211_hwsim: claim CSA support for AP Karl Beldan
2013-12-03 12:55 ` Johannes Berg
2013-12-05 17:26 ` Karl Beldan
2013-12-16 12:51 ` Johannes Berg [this message]
2013-12-17 16:01 ` Kalle Valo
2014-01-06 18:01 ` Karl Beldan
2014-01-07 15:33 ` Johannes Berg
2014-01-07 17:34 ` Karl Beldan
2014-01-20 11:09 ` Johannes Berg
2014-01-20 13:51 ` Karl Beldan
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=1387198314.4665.27.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrei.otcheretianski@intel.com \
--cc=karl.beldan@gmail.com \
--cc=karl.beldan@rivierawaves.com \
--cc=linux-wireless@vger.kernel.org \
--cc=siwu@hrz.tu-chemnitz.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;
as well as URLs for NNTP newsgroup(s).