linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Joe Perches <joe@perches.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: ratelimit few aggregated messages
Date: Thu, 7 Jun 2012 12:41:08 +0530	[thread overview]
Message-ID: <4FD0540C.5060808@qca.qualcomm.com> (raw)
In-Reply-To: <1339050308.6009.9.camel@joe2Laptop>

Hi Joe,

On Thursday 07 June 2012 11:55 AM, Joe Perches wrote:
> On Thu, 2012-06-07 at 11:32 +0530, Mohammed Shafi Shajakhan wrote:
>> From: Mohammed Shafi Shajakhan<mohammed@qca.qualcomm.com>
>>
>> ratelimit few aggregation related messages, these messages
>> floods the log when aggregation is disabled in the AP(for some
>> wifi testcases) and we run traffic between STA and AP.
>
> I looked at all of the #ifdef CONFIG_MAC80211_HT_DEBUG uses.
>
> I think it's better simply to define a mac80211_ht_dbg
> macro for each of the !CONFIG and CONFIG cases and convert
> all of the other #ifdef CONFIG_MAC80211_HT_DEBUG logging
> messages.

oh, ok.

>
> #ifdef CONFIG_MAC80211_HT_DEBUG
> #define mac80211_ht_dbg(fmt, ...)				\
> 	net_dbg_ratelimited(fmt, ##__VA_ARGS__)
> #else
> #define mac80211_ht_dbg(fmt, ...)				\
> do {								\
> 	if (0)							\
> 		net_dbg_ratelimited(fmt, ##__VA_ARGS__);	\
> } while (0)
>
> etc...
>
> I think there's one use of wiphy_dbg that could be a
> mac80211_ht_dbg without much loss.
>
> Maybe add "%s", wiphy_name() to the args there.
>

sorry, i could not understand with wiphy_debug, with mac80211_ht_debug. 
the later is for HT and aggregation related messages.

-- 
thanks,
shafi

  reply	other threads:[~2012-06-07  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  6:02 [PATCH] mac80211: ratelimit few aggregated messages Mohammed Shafi Shajakhan
2012-06-07  6:15 ` Sujith Manoharan
2012-06-07  6:27   ` Mohammed Shafi Shajakhan
2012-06-07  6:25 ` Joe Perches
2012-06-07  7:11   ` Mohammed Shafi Shajakhan [this message]
2012-06-07  7:24     ` Joe Perches
2012-06-07  7:37       ` Mohammed Shafi Shajakhan
2012-06-07  7:57         ` Joe Perches
2012-06-07  8:38           ` Mohammed Shafi Shajakhan
2012-06-07 19:52             ` Joe Perches
2012-06-13  4:59               ` Mohammed Shafi Shajakhan
2012-06-14  1:13                 ` Joe Perches
2012-06-14  4:37                   ` Mohammed Shafi Shajakhan

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=4FD0540C.5060808@qca.qualcomm.com \
    --to=mohammed@qca.qualcomm.com \
    --cc=joe@perches.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).