From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
Subject: Re: question: crda timeout in cfg80211
Date: Tue, 09 Apr 2019 10:40:05 +0200 [thread overview]
Message-ID: <f6b699b051cd1625da57b224e7cd1a8ac6916e72.camel@sipsolutions.net> (raw)
In-Reply-To: <20190409083551.g27qvcxqhfm2x4uq@bars>
On Tue, 2019-04-09 at 08:35 +0000, Sergey Matyukevich wrote:
> Indeed, it is PI. I should have known. But instead I spent some time
> digging through 802.11 specs :)
Oops :)
> Well, as I mentioned in my question, regulatory update/reset operations
> shall be completed in ~pi seconds for _all_ the wireless cards in the
> system. In our case, regulatory reset operation may be fairly costly.
> As a result, we end up with recurring reset timeout, when more than one
> qtn card is installed in a single pcie host. One option for us is to
> optimize regulatory reset operations in firmware.
>
> But what do you think about converting crda_timeout into a per-wiphy
> timeout in the case when all wiphy-s are being processed, e.g.
> in update_all_wiphy_regulatory.
Maybe we should parallelize it? But I don't know how easy that would be.
I'm a little worried just making it longer will cause users to really be
wondering what's going on?
johannes
next prev parent reply other threads:[~2019-04-09 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:42 question: crda timeout in cfg80211 Sergey Matyukevich
2019-04-08 19:06 ` Johannes Berg
2019-04-09 8:35 ` Sergey Matyukevich
2019-04-09 8:40 ` Johannes Berg [this message]
2019-04-11 12:40 ` Sergey Matyukevich
2019-04-23 12:31 ` 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=f6b699b051cd1625da57b224e7cd1a8ac6916e72.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.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