Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: tamizh.raja@oss.qualcomm.com
Cc: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
	jjohnson@kernel.org, jtornosm@redhat.com,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4 1/4] wifi: ath11k: use queue mapping for WCN6750 ring selection
Date: Thu, 30 Jul 2026 08:13:53 +0200	[thread overview]
Message-ID: <20260730061355.212639-1-jtornosm@redhat.com> (raw)
In-Reply-To: <CABkEBKZ7+Z=DL5scE7LnFQz==c3JKoUfFgfDYRf5HoLS_=fr=g@mail.gmail.com>

Hello Tamizh,

> Sure thanks for the information. Do we have throughput values with
> this change?

I don't have WCN6750 hardware, but since WCN7850 (ath12k) already
uses skb_get_queue_mapping() for ring selection, I tested on
WCN7850 comparing queue mapping vs hash based ring selection with
the following change:

  static u8 ath12k_wifi7_hw_get_ring_selector_wcn7850(struct sk_buff *skb)
  {
  -       return skb_get_queue_mapping(skb);
  +       return skb_get_hash(skb);
  }

The hash based test was done on top of the v3 tx flow control
series, which is needed to get stable throughput results.

Results (100s iperf3 TCP TX, open radio environment with VMs):

  skb_get_queue_mapping: 764 Mbits/sec (8.89 GB, 19 retries)
  skb_get_hash:          744 Mbits/sec (8.67 GB, 25 retries)

Throughput is comparable with no measurable regression from using
queue mapping based ring selection.

Note that VM-based testing may not reach peak hardware throughput,
but I think it is sufficient to compare the two ring selection
methods under identical conditions.

Thanks

Best regards
José Ignacio


  reply	other threads:[~2026-07-30  6:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  5:31 [PATCH v4 0/4] ath11k/ath12k: implement TX flow control Jose Ignacio Tornos Martinez
2026-07-24  5:31 ` [PATCH v4 1/4] wifi: ath11k: use queue mapping for WCN6750 ring selection Jose Ignacio Tornos Martinez
2026-07-24  9:04   ` Tamizh Raja
2026-07-24  9:42     ` Jose Ignacio Tornos Martinez
2026-07-29 16:04       ` Tamizh Raja
2026-07-30  6:13         ` Jose Ignacio Tornos Martinez [this message]
2026-07-24  5:31 ` [PATCH v4 2/4] wifi: ath11k/ath12k: remove skb parameter from get_ring_selector Jose Ignacio Tornos Martinez
2026-07-24  5:31 ` [PATCH v4 3/4] wifi: ath11k: implement custom wake_tx_queue with flow control Jose Ignacio Tornos Martinez
2026-07-24  5:31 ` [PATCH v4 4/4] wifi: ath12k: " 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=20260730061355.212639-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 \
    --cc=tamizh.raja@oss.qualcomm.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