All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>, <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 2/2] ath6kl: Complete failed tx packet in ath6kl_htc_tx_from_queue()
Date: Fri, 27 Apr 2012 12:22:43 +0530	[thread overview]
Message-ID: <4F9A423B.102@qca.qualcomm.com> (raw)
In-Reply-To: <4F9A3DEE.207@qca.qualcomm.com>



On Friday 27 April 2012 12:04 PM, Kalle Valo wrote:
> On 04/27/2012 07:09 AM, Vasanthakumar Thiagarajan wrote:
>
>>>>    	bus_req = ath6kl_sdio_alloc_busreq(ar_sdio);
>>>>
>>>> -	if (!bus_req)
>>>> +	if (!bus_req) {
>>>> +		ath6kl_err("Ran out of bus request buffer for tx\n");
>>>>    		return -ENOMEM;
>>>> +	}
>>>
>>> I'm not sure about this one. There's a risk that this will spam the log.
>>> Should it be a debug message instead? Or should we have instead
>>> ath6kl_err_ratelimit()?
>>
>> This condition is very rare, I found it only through code review. I'm
>> pretty sure we don't hit this very often.
>
> I'm not worried how often it happens, I'm just worried that _when_ it
> happens the warning might make things worse. For example, I personally
> saw a case where flood of warnings prevented watchdog heartbeat from
> happening which caused the whole system to reboot. Without the warnings
> system would have worked just fine, just a bit more slowly.

Fair enough.

>
> Is it ok for you if I change the ath6kl_err() to WARN_ON_ONCE() (or
> WARN_ONCE() if you prefer to keep the warning message)? This should be a
> rare event anyway.

I'm fine with that, thanks.

Vasanth

  reply	other threads:[~2012-04-27  6:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 14:56 [PATCH 1/2] ath6kl: Update netstats for some of the tx failrues in ath6kl_data_tx() Vasanthakumar Thiagarajan
2012-04-26 14:56 ` [PATCH 2/2] ath6kl: Complete failed tx packet in ath6kl_htc_tx_from_queue() Vasanthakumar Thiagarajan
2012-04-26 18:21   ` Kalle Valo
2012-04-27  4:09     ` Vasanthakumar Thiagarajan
2012-04-27  6:34       ` Kalle Valo
2012-04-27  6:52         ` Vasanthakumar Thiagarajan [this message]
2012-04-30  7:57 ` [PATCH 1/2] ath6kl: Update netstats for some of the tx failrues in ath6kl_data_tx() Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2012-05-22  7:22 [PATCH] ath6kl: Fix missing gpio pin 9 configuration Vasanthakumar Thiagarajan
2012-05-22  7:22 ` [PATCH 2/2] ath6kl: Complete failed tx packet in ath6kl_htc_tx_from_queue() Vasanthakumar Thiagarajan
2012-05-22  7:25   ` Vasanthakumar Thiagarajan
2012-05-22 12: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=4F9A423B.102@qca.qualcomm.com \
    --to=vthiagar@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.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 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.