All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Alexander Wetzel <alexander@wetzel-home.de>,
	linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
	ath10k@lists.infradead.org, Remi Pommarel <repk@triplefau.lt>
Subject: Re: [PATCH v2 00/10] Convert mac80211 to TXQs only
Date: Thu, 20 Feb 2025 05:56:54 -0800	[thread overview]
Message-ID: <ebeb4471-9c89-4b33-9889-b87f2d218508@gmail.com> (raw)
In-Reply-To: <6586339a-d9c5-4787-95e4-202368341541@wetzel-home.de>

Hi,

On 2/19/25 1:27 PM, Alexander Wetzel wrote:
> On 19.02.25 20:19, James Prestwood wrote:
> ...
>>>
>> Trying to get some clarity if this might fix a regression [1] with 
>> ath10k where upon roaming the TX queue hangs on flush for ~4-10 
>> seconds. I was hopeful for another set [2] but it looks like this 
>> only effected AP mode and with that applied I still notice the behavior.
>>
>> In the worse case we see two failures, which add up to about 10 
>> seconds of delays, more often its just the single "failed to flush 
>> transmit queue"
>>
>> Feb 19 14:15:59 kernel: ath10k_pci 0000:02:00.0: failed to flush sta 
>> txq (sta 6a:3a:0e:22:45:08 skip 0 ar-state 1): 0
>> Feb 19 14:16:04 kernel: ath10k_pci 0000:02:00.0: failed to flush 
>> transmit queue (skip 0 ar-state 1): 0
>>
>> Crossing my fingers this set will have some positive effect here
>>
>
> I had a quick look at ath10k driver and the error message you have. 
> The patch series here will probably not help with that. From driver 
> perspective nothing relevant should be different...
Well thank you for looking at least, I appreciate that.
>
>
>> [1] https://lore.kernel.org/all/ 
>> CA+Xfe4FjUmzM5mvPxGbpJsF3SvSdE5_wgxvgFJ0bsdrKODVXCQ@mail.gmail.com/
>> [2] https://lore.kernel.org/linux-wireless/ 
>> cover.1732293922.git.repk@triplefau.lt/
>>
>> Thanks,
>>
>> James
>>
>


      reply	other threads:[~2025-02-20 14:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17  8:17 [PATCH v2 00/10] Convert mac80211 to TXQs only Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 01/10] wifi: mac80211: move rate control setup Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 02/10] wifi: mac80211: Always provide the MMPDU TXQ Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 03/10] wifi: mac80211: Convert vif->txq to an array Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 04/10] wifi: mac80211: Add new TX queues to replace legacy TX Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 05/10] wifi: mac80211: Stop using legacy TX path Alexander Wetzel
2025-02-17 22:33   ` kernel test robot
2025-02-17  8:17 ` [PATCH v2 06/10] wifi: mac80211: Call ieee80211_tx_h_select_key only once Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 07/10] wifi: mac80211: Rename IEEE80211_TX_INTFL_OFFCHAN_TX_OK Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 08/10] wifi: mac80211: Simplify AMPDU handling Alexander Wetzel
2025-02-17 16:30   ` kernel test robot
2025-02-17  8:17 ` [PATCH v2 09/10] wifi: mac80211: Migrate TX to kthread Alexander Wetzel
2025-02-17  8:17 ` [PATCH v2 10/10] wifi: mac80211: Cleanup *ieee80211_wake_txq* naming Alexander Wetzel
2025-02-19 19:19 ` [PATCH v2 00/10] Convert mac80211 to TXQs only James Prestwood
2025-02-19 21:27   ` Alexander Wetzel
2025-02-20 13:56     ` James Prestwood [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=ebeb4471-9c89-4b33-9889-b87f2d218508@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=alexander@wetzel-home.de \
    --cc=ath10k@lists.infradead.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=repk@triplefau.lt \
    /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.