public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Baochen Qiang <quic_bqiang@quicinc.com>
Cc: <ath12k@lists.infradead.org>,  <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] wifi: ath12k: some improvement to RX throughput
Date: Wed, 17 Jan 2024 15:46:52 +0200	[thread overview]
Message-ID: <874jfc5ayb.fsf@kernel.org> (raw)
In-Reply-To: <20231129020414.56425-1-quic_bqiang@quicinc.com> (Baochen Qiang's message of "Wed, 29 Nov 2023 10:04:11 +0800")

Baochen Qiang <quic_bqiang@quicinc.com> writes:

> Some fields of hal_reo_update_rx_queue are wrongly
> defined, fix it in the first patch.
>
> Currently the maximum block ACK window size is 256,
> with the second patch, it is extended to BA1024.
>
> The small MAC buffer ring becomes the bottle neck
> in RX throughput test, so enlarge its size to get
> a better peak result. This is done is the third patch.
>
> With above three changes, more than 6% increase is
> seen in RX throughput test.
>
> v2:
>  1. wifi: ath12k: fix wrong definitions of hal_reo_update_rx_queue
> 	no change.
>  2. wifi: ath12k: add support for BA1024
> 	a) s/doen/done
> 	b) update struct hal_rx_reo_queue_1k
>  3. wifi: ath12k: change MAC buffer ring size to 2048
> 	no change.
>
> Baochen Qiang (3):
>   wifi: ath12k: fix wrong definitions of hal_reo_update_rx_queue
>   wifi: ath12k: add support for BA1024
>   wifi: ath12k: change MAC buffer ring size to 2048

I had conflicts, please double check:

https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=1ee7c1872873d82a71e05a4e17cbf9a569bc8ec9
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=4d75db679457b5b7e04271f5174d9128d7d73ecf
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=db549be42740d286ee6ec8b2860b4e4789be2167


-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2024-01-17 13:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29  2:04 [PATCH v2 0/3] wifi: ath12k: some improvement to RX throughput Baochen Qiang
2023-11-29  2:04 ` [PATCH v2 1/3] wifi: ath12k: fix wrong definitions of hal_reo_update_rx_queue Baochen Qiang
2023-11-29 15:35   ` Jeff Johnson
2024-01-18  5:52   ` Kalle Valo
2023-11-29  2:04 ` [PATCH v2 2/3] wifi: ath12k: add support for BA1024 Baochen Qiang
2023-11-29 15:35   ` Jeff Johnson
2023-11-29  2:04 ` [PATCH v2 3/3] wifi: ath12k: change MAC buffer ring size to 2048 Baochen Qiang
2023-11-29 15:35   ` Jeff Johnson
2024-01-17 13:46 ` Kalle Valo [this message]
2024-01-17 15:32   ` [PATCH v2 0/3] wifi: ath12k: some improvement to RX throughput Jeff Johnson
2024-01-18  2:21     ` Baochen Qiang

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=874jfc5ayb.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_bqiang@quicinc.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