All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Cc: Sujith Manoharan <sujith@msujith.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Michal Kazior <michal.kazior@tieto.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: Make HTT fill size configurable
Date: Tue, 13 Jan 2015 16:48:29 +0200	[thread overview]
Message-ID: <87vbka4tz6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54AD103B.40002@qti.qualcomm.com> (Vasanthakumar Thiagarajan's message of "Wed, 7 Jan 2015 16:23:47 +0530")

Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> writes:

>>> 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.

Does the patch below fix that issue? Or is this issue still open?

5de6dfc82f71 ath10k: Fix potential Rx ring corruption

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Cc: Michal Kazior <michal.kazior@tieto.com>,
	Sujith Manoharan <sujith@msujith.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: Make HTT fill size configurable
Date: Tue, 13 Jan 2015 16:48:29 +0200	[thread overview]
Message-ID: <87vbka4tz6.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54AD103B.40002@qti.qualcomm.com> (Vasanthakumar Thiagarajan's message of "Wed, 7 Jan 2015 16:23:47 +0530")

Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com> writes:

>>> 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.

Does the patch below fix that issue? Or is this issue still open?

5de6dfc82f71 ath10k: Fix potential Rx ring corruption

-- 
Kalle Valo

  reply	other threads:[~2015-01-13 14:49 UTC|newest]

Thread overview: 48+ 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-05  4:39 ` Sujith Manoharan
2015-01-07 10:14 ` Michal Kazior
2015-01-07 10:14   ` Michal Kazior
2015-01-07 10:37   ` Sujith Manoharan
2015-01-07 10:37     ` Sujith Manoharan
2015-01-13 14:44     ` Kalle Valo
2015-01-13 14:44       ` Kalle Valo
2015-01-13 20:56       ` Sujith Manoharan
2015-01-13 20:56         ` Sujith Manoharan
2015-01-07 10:53   ` Vasanthakumar Thiagarajan
2015-01-07 10:53     ` Vasanthakumar Thiagarajan
2015-01-13 14:48     ` Kalle Valo [this message]
2015-01-13 14:48       ` Kalle Valo
2015-01-13 15:03 ` Kalle Valo
2015-01-13 15:03   ` Kalle Valo
2015-01-13 21:08   ` Sujith Manoharan
2015-01-13 21:08     ` Sujith Manoharan
2015-01-14  9:22     ` Michal Kazior
2015-01-14  9:22       ` Michal Kazior
2015-01-14  9:50       ` Sujith Manoharan
2015-01-14  9:50         ` Sujith Manoharan
2015-01-14 10:12         ` Michal Kazior
2015-01-14 10:12           ` Michal Kazior
2015-01-15  0:17           ` Sujith Manoharan
2015-01-15  0:17             ` Sujith Manoharan
2015-01-15  7:19           ` Kalle Valo
2015-01-15  7:19             ` Kalle Valo
2015-01-15  7:38     ` Kalle Valo
2015-01-15  7:38       ` Kalle Valo
2015-01-15  7:50       ` Sujith Manoharan
2015-01-15  7:50         ` Sujith Manoharan
2015-01-15  8:09         ` Kalle Valo
2015-01-15  8:09           ` Kalle Valo
2015-01-15  8:16           ` Sujith Manoharan
2015-01-15  8:16             ` Sujith Manoharan
2015-01-15  8:21             ` Sujith Manoharan
2015-01-15  8:21               ` Sujith Manoharan
2015-01-15  8:35               ` Kalle Valo
2015-01-15  8:35                 ` Kalle Valo
2015-01-15  8:47                 ` Sujith Manoharan
2015-01-15  8:47                   ` Sujith Manoharan
2015-01-15  8:32             ` Kalle Valo
2015-01-15  8:32               ` Kalle Valo
2015-01-15  8:43               ` Sujith Manoharan
2015-01-15  8:43                 ` Sujith Manoharan
2015-01-15 23:03                 ` Julian Calaby
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=87vbka4tz6.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.com \
    --cc=sujith@msujith.org \
    --cc=vthiagar@qti.qualcomm.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.