Messages in this thread | | | Date | Sat, 16 Oct 2004 22:14:17 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U4 |
| |
* Adam Heath <doogie@debian.org> wrote:
> > after bootup it makes sense to reset the maximum: > > > > echo 10 > /proc/sys/kernel/preempt_max_latency > > > > because during bootup there are a number of latencies that are one-time > > only. > > So, I did that, and immediately started getting more stack dumps. Are > these things that are interesting, or only informational?
they are informational, if you are evaluating latencies. Feel free to post larger latencies. Right now the threshold for "large" depends - on a fast box i'd say latencies above 200 usecs are worth reporting - but any trace can be interesting. Latencies above 1000 usecs are definitely worth seeing.
stability has the highest priority at the moment, and the other type of non-latency stackdumps (scheduling while atomic, smp_processor_id() warnings or outright kernel oopses) should always be reported if possible.
Ingo - 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/
| |