From: John Crispin <john@phrozen.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org, John Crispin <john@phrozen.org>
Subject: [PATCH 0/3] ath11k: improve TX path
Date: Wed, 20 Nov 2019 21:29:53 +0100 [thread overview]
Message-ID: <20191120202956.4401-1-john@phrozen.org> (raw)
This series improves the TX path. The following numbers
are peak performance measured.
prior to series
[SUM] 30.00-31.00 sec 104 MBytes 874 Mbits/sec
series applied
[SUM] 35.00-36.00 sec 124 MBytes 1.04 Gbits/sec
series applied + tx encap
[SUM] 77.00-78.00 sec 167 MBytes 1.40 Gbits/sec
John Crispin (3):
ath11k: move some tx_status parsing to debugfs code
ath11k: optimise ath11k_dp_tx_completion_handler
ath11k: optimize ath11k_hal_tx_status_parse
drivers/net/wireless/ath/ath11k/debugfs_sta.c | 66 +++++++++-------
drivers/net/wireless/ath/ath11k/dp.c | 16 ++--
drivers/net/wireless/ath/ath11k/dp.h | 11 ++-
drivers/net/wireless/ath/ath11k/dp_tx.c | 79 ++++++++++++-------
drivers/net/wireless/ath/ath11k/hal_tx.c | 73 -----------------
drivers/net/wireless/ath/ath11k/hal_tx.h | 13 +--
6 files changed, 101 insertions(+), 157 deletions(-)
--
2.20.1
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next reply other threads:[~2019-11-20 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 20:29 John Crispin [this message]
2019-11-20 20:29 ` [PATCH 1/3] ath11k: move some tx_status parsing to debugfs code John Crispin
2019-11-29 8:32 ` Kalle Valo
2019-11-20 20:29 ` [PATCH 2/3] ath11k: optimise ath11k_dp_tx_completion_handler John Crispin
2019-11-20 20:29 ` [PATCH 3/3] ath11k: optimize ath11k_hal_tx_status_parse John Crispin
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=20191120202956.4401-1-john@phrozen.org \
--to=john@phrozen.org \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.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