Mathieu Desnoyers <[EMAIL PROTECTED]> writes: >> [...] >> > I totally agree with Ingo here. Having a basic instrumentation that is >> > enabled by default will help to identify code paths causing unexpected >> > delays in the kernel. [...] > >> It is. See: CONFIG_VM_EVENT_COUNTERS and all the other vm specific >> crap littered in /proc/ (buddyinfo, zoneinfo, meminfo, etc). [...]
> Isn't the actual instrumentation present in the VM subsystem > consisting mostly of event counters ? This kind of profiling > provides limited help in following specific delays in the > kernel. [...] These existing VM events/counters could be a good target for a second worked-out example (after blktrace) of reimplementation using generic markers. - FChE - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
