mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: jtornosm@redhat.com
Cc: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
	jjohnson@kernel.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v7 0/4] ath11k/ath12k: implement TX flow control
Date: Tue, 13 Oct 2026 18:46:38 +0200	[thread overview]
Message-ID: <20261013164639.237064-1-jtornosm@redhat.com> (raw)
In-Reply-To: <20260917064825.12747-1-jtornosm@redhat.com>

Hi Jeff,
 
Friendly follow-up on this series. v7 addressed your spin_lock_bh
comment, and I replied to the rcu_dereference_bh question explaining
why ath12k differs from the ath9k case (happy to do it as a follow-up
if you'd like). My results with VMs are much better with the TX control,
and I think it can help baremetal too.

Any feedback on v7, anything else I can do?
At least, would it be acceptable for ath11k?
For ath12k, if the concern is the locking, the rcu_dereference_bh
refactoring would require changes to existing mac_op_tx code. Is that
the direction you want?
 
Thanks
 
Best regards
José Ignacio


  parent reply	other threads:[~2026-10-13 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  6:48 Jose Ignacio Tornos Martinez
2026-09-17  6:48 ` [PATCH v7 1/4] wifi: ath11k: use queue mapping for WCN6750 ring selection Jose Ignacio Tornos Martinez
2026-09-17  6:48 ` [PATCH v7 2/4] wifi: ath11k/ath12k: remove skb parameter from get_ring_selector Jose Ignacio Tornos Martinez
2026-09-17  6:48 ` [PATCH v7 3/4] wifi: ath11k: implement custom wake_tx_queue with flow control Jose Ignacio Tornos Martinez
2026-09-17  6:48 ` [PATCH v7 4/4] wifi: ath12k: " Jose Ignacio Tornos Martinez
2026-10-13 16:46 ` Jose Ignacio Tornos Martinez [this message]
2026-10-14 16:23 ` [PATCH v7 0/4] ath11k/ath12k: implement TX " Tamizh Raja
2026-10-17  7:40   ` Jose Ignacio Tornos Martinez

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=20261013164639.237064-1-jtornosm@redhat.com \
    --to=jtornosm@redhat.com \
    --cc=ath11k@lists.infradead.org \
    --cc=ath12k@lists.infradead.org \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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®