From: Johannes Berg <johannes@sipsolutions.net>
To: "Nerijus Bendžiūnas" <nerijus.bendziunas@gmail.com>,
linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mac80211: skip reconfiguration when the last emulated chanctx goes
Date: Thu, 03 Sep 2026 19:35:22 +0200 [thread overview]
Message-ID: <22c0379159aaaf58c8d7a9dd36cd97dbf1a9e10b.camel@sipsolutions.net> (raw)
In-Reply-To: <20260829101532.1471682-1-nerijus.bendziunas@gmail.com> (sfid-20260829_121548_636837_D7BF5AEB)
On Sat, 2026-08-29 at 13:15 +0300, Nerijus Bendžiūnas wrote:
> Drivers without native channel contexts get the emulated ops, and
> ieee80211_emulate_remove_chanctx() reconfigures the hardware with no
> context left, which ieee80211_calc_hw_conf_chan() turns into a channel
> change to the default channel. A monitor-mode retune releases its
> context before using the next one, so every retune costs the driver two
> channel changes: one to the default channel and one to the channel that
> was asked for. Nothing is on the air without a context and the next
> context sets the channel, so drop that reconfiguration; the radar flag
> is still cleared for the next configuration to carry.
>
> On an AR9271 (ath9k_htc), where every channel change is a full reset
> over USB, hopping across the 13 standard 2.4 GHz channels with an
> unmodified driver showed 2006 drv_config CHANGE_CHANNEL calls for 1000
> hops with the reconfiguration and 1006 without, a median hop of 123.5 ms
> against 92.0 ms (p95 183 ms against 105 ms), and 99.1% against 98.3% of
> injected frames delivered on a second card.
>
> Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
You're expected to disclose LLM usage.
https://www.kernel.org/doc/html/latest/process/coding-assistants.html
And please clean up the wordering everywhere before submitting again.
johannes
prev parent reply other threads:[~2026-09-03 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 10:15 Nerijus Bendžiūnas
2026-09-03 17:35 ` 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=22c0379159aaaf58c8d7a9dd36cd97dbf1a9e10b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nerijus.bendziunas@gmail.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
all inboxes | Powered by JetHome®