linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: simon.wunderlich@openmesh.com,
	Daniel Bailey <daniel.bailey@openmesh.com>,
	Shashidhar Lakkavalli <shashidhar.lakkavalli@openmesh.com>,
	linux-wireless@vger.kernel.org
Subject: mac80211: AQM and block_tx
Date: Thu, 05 Jul 2018 10:47:11 +0200	[thread overview]
Message-ID: <2846230.fHgAC8qB8Q@bentobox> (raw)

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

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.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-07-05  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  8:47 Sven Eckelmann [this message]
2018-07-10  6:55 ` mac80211: AQM and block_tx Sven Eckelmann
2018-07-10 12:09   ` Toke Høiland-Jørgensen
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=2846230.fHgAC8qB8Q@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=daniel.bailey@openmesh.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shashidhar.lakkavalli@openmesh.com \
    --cc=simon.wunderlich@openmesh.com \
    --cc=toke@toke.dk \
    /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).