From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from perches-mx.perches.com ([206.117.179.246]:43152 "EHLO labridge.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757065Ab2EOR70 (ORCPT ); Tue, 15 May 2012 13:59:26 -0400 Message-ID: <1337104765.7050.24.camel@joe2Laptop> (sfid-20120515_195955_463081_DA730895) Subject: Re: [RFC net-next 0/2] net: Use net__ratelimit From: Joe Perches To: David Miller Cc: netdev@vger.kernel.org, linux-decnet-user@lists.sourceforge.net, netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org, coreteam@netfilter.org, linux-wireless@vger.kernel.org, dev@openvswitch.org, linux-sctp@vger.kernel.org, linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org Date: Tue, 15 May 2012 10:59:25 -0700 In-Reply-To: <20120515.134531.530903973750646107.davem@davemloft.net> References: <20120515.134531.530903973750646107.davem@davemloft.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, 2012-05-15 at 13:45 -0400, David Miller wrote: > From: Joe Perches > Date: Mon, 14 May 2012 00:56:24 -0700 > > > net_ratelimit() like __ratelimit() is too easy to misuse. > > > > Add simplifying macros similar to pr__ratelimited > > that combines the test of net_ratelimit and logging. > > > > Joe Perches (2): > > net: Add net_ratelimited_function and net__ratelimited macros > > net: Convert net_ratelimit uses to net__ratelimited > > These look fine to me so I've applied them to net-next and am > sanity checking the build right now. OK, but fyi, there's a possible issue with !CONFIG_DEBUG builds because these patches converted some uses of if (net_ratelimit()) printk(KERN_DEBUG ... to net_dbg_ratelimited() These messages are no longer emitted when DEBUG isn't defined and not using dynamic_debug. I'm not sure that's a real problem, but it's a difference. I could produce a net_printk_ratelimited that would keep the original behavior if necessary. net_printk_ratelimited(KERN_DEBUG etc...) cheers, Joe