[patch] latency tracer, 2.6.15-rc7
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Thu, 29 Dec 2005 09:22:17 +0100
* Lee Revell <rlrevell@xxxxxxxxxxx> wrote:
> I'm not sure how much work it would be to break out
> CONFIG_LATENCY_TRACE as a separate patch.
could you check out the 2.6.15-rc7 version of the latency tracer i
uploaded to:
http://redhat.com/~mingo/latency-tracing-patches/
could test it by e.g. trying to reproduce the same VM latency as in the
-rt tree. [the two zlib patches are needed if you are using 4K stacks,
mcount increases stack footprint.]
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch] latency tracer, 2.6.15-rc7
- From: Dave Jones
- Re: [patch] latency tracer, 2.6.15-rc7
- References:
- 2.6.15-rc5: latency regression vs 2.6.14 in exit_mmap->free_pgtables
- From: Lee Revell
- Re: 2.6.15-rc5: latency regression vs 2.6.14 in exit_mmap->free_pgtables
- From: Hugh Dickins
- Re: 2.6.15-rc5: latency regression vs 2.6.14 in exit_mmap->free_pgtables
- From: Lee Revell
- 2.6.15-rc5: latency regression vs 2.6.14 in exit_mmap->free_pgtables
- Prev by Date: Re: [PATCH 6 of 20] ipath - driver debugging headers
- Next by Date: Re: [RFC] CPU scheduler: Simplified interactive bonus mechanism
- Previous by thread: Re: 2.6.15-rc5: latency regression vs 2.6.14 in exit_mmap->free_pgtables
- Next by thread: Re: [patch] latency tracer, 2.6.15-rc7
- Index(es):