All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath11k: Enable threaded NAPI on WCN6750
Date: Fri, 2 Sep 2022 18:24:23 +0530	[thread overview]
Message-ID: <6fd6c592-3bad-ce39-24ea-e28d5ad98e7b@quicinc.com> (raw)
In-Reply-To: <166212222808.10242.13626602156198198987.kvalo@kernel.org>

On 9/2/2022 6:07 PM, Kalle Valo wrote:
> Manikanta Pubbisetty <quic_mpubbise@quicinc.com> wrote:
> 
>> Enable threaded NAPI on WCN6750. Unlike traditional NAPI poll which
>> runs in softirq context and on the core which scheduled the NAPI,
>> threaded NAPI makes use of kernel threads which are under direct
>> control of the scheduler and helps in balancing the NAPI processing
>> load across multiple CPUs thereby improving throughput.
>>
>> In the case of WCN6750, enabling threaded NAPI has improved
>> 160 MHz RX throughput by nearly 400 Mbps. This should give similar
>> gains for other ath11k devices as well, therefore enable threaded
>> NAPI on all other devices.
>>
>> Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1
>>
>> Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
> 
> Fails to apply and no base commit provided, so please rebase.
> 
> error: patch failed: drivers/net/wireless/ath/ath11k/core.c:111
> error: drivers/net/wireless/ath/ath11k/core.c: patch does not apply
> error: patch failed: drivers/net/wireless/ath/ath11k/hw.h:205
> error: drivers/net/wireless/ath/ath11k/hw.h: patch does not apply
> stg import: Diff does not apply cleanly
> 
> 3 patches set to Changes Requested.
> 
> 12924009 [1/3] ath11k: Enable threaded NAPI on WCN6750
> 12924011 [2/3] ath11k: Add multi TX ring support for WCN6750
> 12924010 [3/3] ath11k: Increase TCL data ring size for WCN6750
> 

Sure, thanks!

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/3] ath11k: Enable threaded NAPI on WCN6750
Date: Fri, 2 Sep 2022 18:24:23 +0530	[thread overview]
Message-ID: <6fd6c592-3bad-ce39-24ea-e28d5ad98e7b@quicinc.com> (raw)
In-Reply-To: <166212222808.10242.13626602156198198987.kvalo@kernel.org>

On 9/2/2022 6:07 PM, Kalle Valo wrote:
> Manikanta Pubbisetty <quic_mpubbise@quicinc.com> wrote:
> 
>> Enable threaded NAPI on WCN6750. Unlike traditional NAPI poll which
>> runs in softirq context and on the core which scheduled the NAPI,
>> threaded NAPI makes use of kernel threads which are under direct
>> control of the scheduler and helps in balancing the NAPI processing
>> load across multiple CPUs thereby improving throughput.
>>
>> In the case of WCN6750, enabling threaded NAPI has improved
>> 160 MHz RX throughput by nearly 400 Mbps. This should give similar
>> gains for other ath11k devices as well, therefore enable threaded
>> NAPI on all other devices.
>>
>> Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1
>>
>> Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
> 
> Fails to apply and no base commit provided, so please rebase.
> 
> error: patch failed: drivers/net/wireless/ath/ath11k/core.c:111
> error: drivers/net/wireless/ath/ath11k/core.c: patch does not apply
> error: patch failed: drivers/net/wireless/ath/ath11k/hw.h:205
> error: drivers/net/wireless/ath/ath11k/hw.h: patch does not apply
> stg import: Diff does not apply cleanly
> 
> 3 patches set to Changes Requested.
> 
> 12924009 [1/3] ath11k: Enable threaded NAPI on WCN6750
> 12924011 [2/3] ath11k: Add multi TX ring support for WCN6750
> 12924010 [3/3] ath11k: Increase TCL data ring size for WCN6750
> 

Sure, thanks!

  reply	other threads:[~2022-09-02 12:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 13:51 [PATCH 0/3] Throughput fixes for WCN6750 Manikanta Pubbisetty
2022-07-20 13:51 ` Manikanta Pubbisetty
2022-07-20 13:51 ` [PATCH 1/3] ath11k: Enable threaded NAPI on WCN6750 Manikanta Pubbisetty
2022-07-20 13:51   ` Manikanta Pubbisetty
2022-09-02 12:37   ` Kalle Valo
2022-09-02 12:37     ` Kalle Valo
2022-09-02 12:54     ` Manikanta Pubbisetty [this message]
2022-09-02 12:54       ` Manikanta Pubbisetty
2022-09-02 12:48   ` Kalle Valo
2022-09-02 12:48     ` Kalle Valo
2022-09-02 13:17     ` Manikanta Pubbisetty
2022-09-02 13:17       ` Manikanta Pubbisetty
2022-09-02 13:20       ` Robert Marko
2022-09-02 13:20         ` Robert Marko
2022-09-02 13:42         ` Manikanta Pubbisetty
2022-09-02 13:42           ` Manikanta Pubbisetty
2022-09-02 13:46           ` Robert Marko
2022-09-02 13:46             ` Robert Marko
2022-09-02 14:30             ` Manikanta Pubbisetty
2022-09-02 14:30               ` Manikanta Pubbisetty
2022-09-08  6:46               ` Kalle Valo
2022-09-08  6:46                 ` Kalle Valo
2022-09-08  8:49                 ` Robert Marko
2022-09-08  8:49                   ` Robert Marko
2022-09-08 12:15                   ` Kalle Valo
2022-09-08 12:15                     ` Kalle Valo
2022-09-08  6:49       ` Kalle Valo
2022-09-08  6:49         ` Kalle Valo
2022-07-20 13:51 ` [PATCH 2/3] ath11k: Add multi TX ring support for WCN6750 Manikanta Pubbisetty
2022-07-20 13:51   ` Manikanta Pubbisetty
2022-09-02 12:49   ` Kalle Valo
2022-09-02 12:49     ` Kalle Valo
2022-09-02 13:44     ` Manikanta Pubbisetty
2022-09-02 13:44       ` Manikanta Pubbisetty
2022-07-20 13:51 ` [PATCH 3/3] ath11k: Increase TCL data ring size " Manikanta Pubbisetty
2022-07-20 13:51   ` Manikanta Pubbisetty

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=6fd6c592-3bad-ce39-24ea-e28d5ad98e7b@quicinc.com \
    --to=quic_mpubbise@quicinc.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@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 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.