From: "Valo, Kalle" <kvalo@qca.qualcomm.com>
To: "Manoharan, Rajkumar" <rmanohar@qti.qualcomm.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"rmanohar@codeaurora.org" <rmanohar@codeaurora.org>
Subject: Re: [PATCH 0/9] ath10k: improve throughput performance
Date: Mon, 4 Apr 2016 14:55:16 +0000 [thread overview]
Message-ID: <874mbhe84s.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1458647539-17213-1-git-send-email-rmanohar@qti.qualcomm.com> (Rajkumar Manoharan's message of "Tue, 22 Mar 2016 17:22:10 +0530")
Rajkumar Manoharan <rmanohar@qti.qualcomm.com> writes:
> Hi All,
>
> In order to reuse HTT Rx descriptor (copy engine 5), HTT response
> processing should be decoupled from txrx data processing. This change also
> helps to reduce rx ring lock contention. As txrx tasklet's work load is
> reduced, rx replenish task can be combined with txrx_task. Refilling
> complete rx ring from txrx tasket is affecting UDP UL traffic in AP135
> platform. Hence existing refill threshold is updated to meet peak
> throughput in both AP135 and AP148 platforms. Instead of tasklet existing
> refill timer is used to reschedule replenish work at an interval of 5 ms
> incase of more deficit.
>
> This series are experimented in both AP148(QCA99x0) & IPQ4019 platforms.
> Below are consolidated report alongwith CPU usage. Thanks Tamizh for helping
> to verify the changes.
>
> IPQ4019(TOT) IPQ4019(+rework) AP148(TOT) AP148(+rework)
> =========== =============== ========== =============
> TCP DL 639 (40%) 646 (42%) 1134 (71%) 1134 (71%)
> TCP UL 661 (31%) 663 (30%) 1244 (71%) 1270 (72%)
> UDP DL 670 (50%) 682 (49%) 1240 (73%) 1244 (75%)
>
> AP135 (OpenWrt TOT) AP135 (+changes)
> ================== ===============
>
> TCP DL 603 620
> TCP UL 430 428
> UDP DL 758 803
> UDP UL 420 450
>
> -Rajkumar
>
> Rajkumar Manoharan (9):
> ath10k: speedup htt rx descriptor processing for tx completion
> ath10k: copy tx fetch indication message
> ath10k: remove unused fw_desc processing
> ath10k: cleanup amsdu processing for rx indication
> ath10k: speedup htt rx descriptor processing for rx_ind
> ath10k: register ath10k_htt_htc_t2h_msg_handler
> ath10k: cleanup copy engine receive next completion
> ath10k: reuse copy engine 5 (htt rx) descriptors
> ath10k: combine txrx and replenish task
Applied, thanks.
--
Kalle Valo
prev parent reply other threads:[~2016-04-04 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 11:52 [PATCH 0/9] ath10k: improve throughput performance Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 1/9] ath10k: speedup htt rx descriptor processing for tx completion Rajkumar Manoharan
2016-03-24 13:08 ` Valo, Kalle
2016-03-24 15:52 ` Manoharan, Rajkumar
2016-03-24 16:13 ` Manoharan, Rajkumar
2016-03-29 7:39 ` Valo, Kalle
2016-03-22 11:52 ` [PATCH 2/9] ath10k: copy tx fetch indication message Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 3/9] ath10k: remove unused fw_desc processing Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 4/9] ath10k: cleanup amsdu processing for rx indication Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 5/9] ath10k: speedup htt rx descriptor processing for rx_ind Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 6/9] ath10k: register ath10k_htt_htc_t2h_msg_handler Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 7/9] ath10k: cleanup copy engine receive next completion Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 8/9] ath10k: reuse copy engine 5 (htt rx) descriptors Rajkumar Manoharan
2016-03-22 11:52 ` [PATCH 9/9] ath10k: combine txrx and replenish task Rajkumar Manoharan
2016-04-04 14:55 ` Valo, Kalle [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=874mbhe84s.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmanohar@codeaurora.org \
--cc=rmanohar@qti.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;
as well as URLs for NNTP newsgroup(s).