Messages in this thread | | | Date | Fri, 09 May 2003 12:49:26 -0700 | From | "Martin J. Bligh" <> | Subject | Re: 2.5.69-mm3 |
| |
> 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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |