All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: drago01 <drago01@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Rate limiting AP bandwidth change messages in ieee80211_config_bw?
Date: Thu, 01 Oct 2015 09:48:25 +0200	[thread overview]
Message-ID: <1443685705.1880.6.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+5PVA5L2LwwbJmoxwkYtJ=PYc9Q5g4KpqwmA0urxX8CRe=L+g@mail.gmail.com> (sfid-20151001_020951_577334_ECF74B43)


> For what purpose?  Or rather, when a user sees this in their dmesg,
> what are they supposed to do about it?

I think the idea isn't that the user would do something, but more that
in case of performance issues, or perhaps driver/device bugs handling
the changes, or similar you'd have an indication that this happened.


> > perhaps we should try rate limiting it then? Could you check if 
> > that
> > actually works?
> 
> I'll think on it, sure.  I was hoping sdata_dbg would be sufficient
> because it's much easier, but if there's value in the message I can
> look at limiting it in some fashion.
> 

Thanks.

johannes

      reply	other threads:[~2015-10-01  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 17:02 Rate limiting AP bandwidth change messages in ieee80211_config_bw? Josh Boyer
2015-09-30 18:32 ` Johannes Berg
2015-09-30 19:04   ` Johannes Berg
2015-10-01  0:09     ` Josh Boyer
2015-10-01  7:48       ` Johannes Berg [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=1443685705.1880.6.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=drago01@gmail.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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.