From: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>,
Sujith Manoharan <sujith@msujith.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: Make HTT fill size configurable
Date: Wed, 7 Jan 2015 16:23:47 +0530 [thread overview]
Message-ID: <54AD103B.40002@qti.qualcomm.com> (raw)
In-Reply-To: <CA+BoTQ=HqF0vBj4chXfoY9GKcFBP8Xh37HXo5etDDZ1XCg6O4w@mail.gmail.com>
On Wednesday 07 January 2015 03:44 PM, Michal Kazior wrote:
> On 5 January 2015 at 05:39, Sujith Manoharan <sujith@msujith.org> wrote:
>> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>>
>> The HTT RX ring is replenished with a maximum of 16 buffers,
>> but this might be insufficient when RX traffic is high.
>> Not having enough RX buffers throttles the FW, resulting
>> in low throughput.
>>
>> This patch adds a module parameter to adjust the fill size
>> based on the platform/usage.
>
> I don't think this should be adjustable.
Default value of 16 causes rx ring corruption within 1 hour of stress
testing. Increasing this limit to 1000 solves the issue, not sure what
max value in > 16 and <= 1000 works. This lower value obviously has issues
on some platforms.
Vasanth
next prev parent reply other threads:[~2015-01-07 10:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 4:39 [PATCH] ath10k: Make HTT fill size configurable Sujith Manoharan
2015-01-07 10:14 ` Michal Kazior
2015-01-07 10:37 ` Sujith Manoharan
2015-01-13 14:44 ` Kalle Valo
2015-01-13 20:56 ` Sujith Manoharan
2015-01-07 10:53 ` Vasanthakumar Thiagarajan [this message]
2015-01-13 14:48 ` Kalle Valo
2015-01-13 15:03 ` Kalle Valo
2015-01-13 21:08 ` Sujith Manoharan
2015-01-14 9:22 ` Michal Kazior
2015-01-14 9:50 ` Sujith Manoharan
2015-01-14 10:12 ` Michal Kazior
2015-01-15 0:17 ` Sujith Manoharan
2015-01-15 7:19 ` Kalle Valo
2015-01-15 7:38 ` Kalle Valo
2015-01-15 7:50 ` Sujith Manoharan
2015-01-15 8:09 ` Kalle Valo
2015-01-15 8:16 ` Sujith Manoharan
2015-01-15 8:21 ` Sujith Manoharan
2015-01-15 8:35 ` Kalle Valo
2015-01-15 8:47 ` Sujith Manoharan
2015-01-15 8:32 ` Kalle Valo
2015-01-15 8:43 ` Sujith Manoharan
2015-01-15 23:03 ` Julian Calaby
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=54AD103B.40002@qti.qualcomm.com \
--to=vthiagar@qti.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=sujith@msujith.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;
as well as URLs for NNTP newsgroup(s).