From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Marty Faltesek <mfaltesek@google.com>
Cc: linux-wireless@vger.kernel.org, dgentry@google.com,
ath10k@lists.infradead.org, apenwarr@google.com
Subject: Re: [PATCH v2] ath10k: Improve performance by reducing tx_lock contention.
Date: Wed, 29 Jul 2015 11:27:44 +0300 [thread overview]
Message-ID: <87h9on74hr.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1437597504-25554-1-git-send-email-mfaltesek@google.com> (Marty Faltesek's message of "Wed, 22 Jul 2015 16:38:24 -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 dual-core ARM Freescale LS1024A
> (f.k.a. Mindspeed Comcerto 2000) AP with a 3x3 client from 495 to 580 Mbps.
> Other CPU bound multicore systems may also benefit.
>
> 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>
Thanks, applied.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2015-07-29 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 20:38 [PATCH v2] ath10k: Improve performance by reducing tx_lock contention Marty Faltesek
2015-07-29 8:27 ` 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=87h9on74hr.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=apenwarr@google.com \
--cc=ath10k@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox