Messages in this thread | | | Date | Tue, 23 Nov 2004 11:51:13 -0800 | From | William Lee Irwin III <> | Subject | Re: Debugging a memory leak in the 2.6.X kernel - how-to? |
| |
On Tue, Nov 23, 2004 at 02:29:40PM -0500, Valdis.Kletnieks@vt.edu wrote: > That's checking every 2-3 seconds - about as fast as I could hit > uparrow, enter, and read the numbers and repeat. After I killed > gkrellm, it's sat solidly in the 10380-10400 range for well over an > hour. > *Possibly* related: I'm sitting at about 90% idle, but the load > average is showing as 1.15 - however, I'm *NOT* seeing any processes > stuck in 'D' state in the ps output. > Any advice how to shoot this one?
Use the profile_hit() stuff to register a new profiling type for the slab allocations you're interested in, then the offending allocators should show up close to the top there unless there is a lot of turnover. In that case, fiddling with the profiling and slab code to unregister hits from whoever allocated a buffer should get solid results.
-- wli - 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/
| |