[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.5.69-mm3

To: dipankar@in.ibm.com, Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.69-mm3
From: "Martin J. Bligh" <mbligh@aracnet.com>
Date: Fri, 09 May 2003 12:49:26 -0700
cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Fake-Sender: owner-linux-mm@kvack.org
In-Reply-To: <20030509141012.GD2059@in.ibm.com>
Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
References: <20030508013958.157b27b7.akpm@digeo.com> <20030509141012.GD2059@in.ibm.com>
Sender: Rik van Riel <riel@nl.linux.org>

> 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 ?

I'd find that useful - if it has a measurable overhead. If not, just leave
it on all the time ;-)

M.

--
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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

References:
- 2.5.69-mm3
  - From: Andrew Morton <akpm@digeo.com>
- Re: 2.5.69-mm3
  - From: Dipankar Sarma <dipankar@in.ibm.com>

Prev by Date: Re: 2.5.69-mm3
Next by Date: Re: Extended Pagins on IA32
Prev by thread: Re: 2.5.69-mm3
Next by thread: Re: 2.5.69-mm3
Index(es):
- Date
- Thread