From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: simon.wunderlich@openmesh.com,
Daniel Bailey <daniel.bailey@openmesh.com>,
Shashidhar Lakkavalli <shashidhar.lakkavalli@openmesh.com>,
linux-wireless@vger.kernel.org
Subject: Re: mac80211: AQM and block_tx
Date: Tue, 10 Jul 2018 14:09:57 +0200 [thread overview]
Message-ID: <87wou3cmwa.fsf@toke.dk> (raw)
In-Reply-To: <4554238.GrJkgPgAWi@bentobox>
Sven Eckelmann <sven.eckelmann@openmesh.com> writes:
> On Donnerstag, 5. Juli 2018 10:47:11 CEST Sven Eckelmann wrote:
>> Hi Toke,
>>
>> we are currently testing DFS with ath10k and noticed that AQM seems to ignore
>> cfg80211_csa_settings->block_tx. Problem is now that the channel switch is
>> started on a detected radar
>>
>> echo 1 >/sys/kernel/debug/ieee80211/phy1/ath10k/dfs_simulate_radar
>>
>> NL80211_ATTR_CH_SWITCH_BLOCK_TX is set for the channel switch by hostapd but
>> the AP still sends QoS data to the client.
>>
>> Was there a fix for such a problem which I might have missed? I've just worked
>> around that by setting wake_tx_queue TO NULL in ath10k. This still must be
>> verified but at least I didn't see any packets anymore on a monitor interface.
>
>
> Just as information, the ath10k Dakota devices went through DFS
> certification
Cool! (I think? Not quite sure what the implications of passing / not
passing certification are?)
> but the AQM had to be disabled. Otherwise we would have had problems
> with the FCC closing time.
Hmm, too bad; but I guess this can be fixed :)
-Toke
next prev parent reply other threads:[~2018-07-10 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 8:47 mac80211: AQM and block_tx Sven Eckelmann
2018-07-10 6:55 ` Sven Eckelmann
2018-07-10 12:09 ` Toke Høiland-Jørgensen [this message]
2018-07-10 12:39 ` Manikanta Pubbisetty
2018-07-10 13:40 ` Sven Eckelmann
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=87wou3cmwa.fsf@toke.dk \
--to=toke@toke.dk \
--cc=daniel.bailey@openmesh.com \
--cc=linux-wireless@vger.kernel.org \
--cc=shashidhar.lakkavalli@openmesh.com \
--cc=simon.wunderlich@openmesh.com \
--cc=sven.eckelmann@openmesh.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.