- Subject: Re: [RFC net-next 0/2] net: Use net_<level>_ratelimit
- From: Johannes Berg <johannes@xxxxxxxxxxxxxxxx>
- Date: Tue, 15 May 2012 20:29:08 +0200
- Cc: joe@xxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, linux-decnet-user@xxxxxxxxxxxxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxx, netfilter@xxxxxxxxxxxxxxx, coreteam@xxxxxxxxxxxxx, linux-wireless@xxxxxxxxxxxxxxx, dev@xxxxxxxxxxxxxxx, linux-sctp@xxxxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
- In-reply-to: <20120515.142405.633851408201128056.davem@davemloft.net>
- References: <1337105028.15553.3.camel@jlt3.sipsolutions.net> <20120515.141348.892964316296815698.davem@davemloft.net> <1337106094.15553.5.camel@jlt3.sipsolutions.net> <20120515.142405.633851408201128056.davem@davemloft.net>
On Tue, 2012-05-15 at 14:24 -0400, David Miller wrote:
> > But don't you have to do something in the sources to actually get
> > dynamic_debug enabled? I'm concerned this will make mac80211 debugging
> > inconsistent - the normal bits are just printk() still, and the
> > rate-limited bits need some special enabling? That seems odd.
>
> You can turn them all off or on with a simple flip of a boolean switch
> at run-time. Or, alternatively, you can turn them on or off in a
> finer grained manner with other run-time facilities.
>
> There should be a transition away from explicit KERN_DEBUG.
I support that, but I think it's confusing to have things mixed. Also,
we seem to have printk_ratelimit(), so I'd prefer to have that used in
mac80211 instead until everything there moves over to newer facilities.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux USB Development]
[Linux Media Development]
[Video for Linux]
[Linux NILFS]
[Linux Audio Users]
[Photo]
[Yosemite Info]
[Yosemite Photos]
[POF Sucks]
[Linux Kernel]
[Linux SCSI]
[XFree86]