From: Kalle Valo <kvalo@codeaurora.org>
To: Avery Pennarun <apenwarr@google.com>
Cc: Marty Faltesek <mfaltesek@google.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Denton Gentry <dgentry@google.com>
Subject: Re: [PATCH] ath10k: Improve performance by reducing tx_lock contention.
Date: Wed, 22 Jul 2015 09:28:16 +0300 [thread overview]
Message-ID: <87si8gln9b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAPp0ZBavC33umwjraqtxpKWP6Ez9X1_7K9fZNsP2oPu4v=uyEw@mail.gmail.com> (Avery Pennarun's message of "Wed, 22 Jul 2015 02:21:27 -0400")
Avery Pennarun <apenwarr@google.com> writes:
> On Wed, Jul 22, 2015 at 2:16 AM, Kalle Valo <kvalo@codeaurora.org> wrote:
>> 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?
>
> That's a good idea to mention in the commit message, although given
> that it's just an in-driver lock contention patch, it probably affects
> any underpowered multicore CPU.
Yeah, that would be good to mention as well :)
--
Kalle Valo
prev parent reply other threads:[~2015-07-22 6:28 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
2015-07-22 6:21 ` Avery Pennarun
2015-07-22 6:28 ` Kalle Valo [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=87si8gln9b.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.