Re: [PATCH] Instrumenting high latency
From: William Lee Irwin III (wli_at_holomorphy.com)
Date: 07/12/04
- Previous message: ·ÉÒ»´Î: "(no subject)"
- In reply to: Rajput: "Re: [PATCH] Instrumenting high latency"
- Next in thread: Martin J. Bligh: "Re: [PATCH] Instrumenting high latency"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 12 Jul 2004 03:44:42 -0700 To: Rajput <rajput@indo.net>
On Mon, Jul 12, 2004 at 04:11:32PM +0530, Rajput wrote:
> what is the difference in interrupt latency with and without your patch.
> Regards,
> Rajput.
This is meant to instrument scheduling latency, it doesn't improve
anything directly. It likely introduces a fair amount of overhead.
In the event a poor preempt_thresh= parameter is chosen, it may render
systems effectively unusable due to endless printk()'ing (which I should
fix via printk_ratelimit() shortly).
I recommend applying and/or enabling this only for diagnostic purposes.
-- 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/
- Previous message: ·ÉÒ»´Î: "(no subject)"
- In reply to: Rajput: "Re: [PATCH] Instrumenting high latency"
- Next in thread: Martin J. Bligh: "Re: [PATCH] Instrumenting high latency"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]