From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 13 May 2003 16:13:04 -0400 (EDT) From: Bill Davidsen Subject: Re: 2.5.69-mm3 In-Reply-To: <20030509141012.GD2059@in.ibm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Dipankar Sarma Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: On Fri, 9 May 2003, Dipankar Sarma wrote: > I am wondering what we should do with this patch. The RCU stats display > the #s of RCU requests and actual updates on each CPU. On a normal system > they don't mean much to a sysadmin, so I am not sure if it is the right > thing to include this feature. OTOH, it is extremely useful to detect > potential memory leaks happening due to, say a CPU looping in > kernel (and RCU not happening consequently). Will a CONFIG_RCU_DEBUG > make it more palatable for mainline ? Are there similar things, inplace or in patches? Perhaps a menu section for kernel metrics and a nice little niche in /proc to display them? Things like this are helpful when tuning a kernel, but perhaps not wanted for the minimalist (like embedded) configs. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org