From: Kalle Valo <kvalo@codeaurora.org>
To: Marty Faltesek <mfaltesek@google.com>
Cc: linux-wireless@vger.kernel.org, dgentry@google.com, apenwarr@google.com
Subject: Re: [PATCH] ath10k: Improve performance by reducing tx_lock contention.
Date: Wed, 22 Jul 2015 09:16:49 +0300 [thread overview]
Message-ID: <87wpxslnse.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1437527130-15232-1-git-send-email-mfaltesek@google.com> (Marty Faltesek's message of "Tue, 21 Jul 2015 21:05:30 -0400")
Marty Faltesek <mfaltesek@google.com> writes:
> From: Qi Zhou <qizhou@google.com>
>
> During tx completion, tx_lock is held for longer than required, preventing
> efficient refill of htt->pending_tx. Refactor the code so that only MSDU
> related operations are protected by the lock.
>
> Improves downstream performance on a 3x3 client from 495 to 580 Mbps.
It would be good to mention the actual platform/CPU as I guess this
improvement is platform specific?
> Signed-off-by: Denton Gentry <dgentry@google.com>
> Signed-off-by: Avery Pennarun <apenwarr@google.com>
> [mfaltesek@google.com: removed conflicting code for tracking msdu_ids.]
> Signed-off-by: Marty Faltesek <mfaltesek@google.com>
>
> Change-Id: Ia0fe8b037033c3335b5632b7276c3b0e33e738d4
No gerrit tags, please.
So that patchwork finds the patch please send it to the ath10k list and
cc linux-wireless as documented here:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/sources#submitting_patches
--
Kalle Valo
next prev parent reply other threads:[~2015-07-22 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 1:05 [PATCH] ath10k: Improve performance by reducing tx_lock contention Marty Faltesek
2015-07-22 6:16 ` Kalle Valo [this message]
2015-07-22 6:21 ` Avery Pennarun
2015-07-22 6:28 ` Kalle Valo
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=87wpxslnse.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=apenwarr@google.com \
--cc=dgentry@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mfaltesek@google.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 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.