On 07/06/2007 07:44 AM, Andi Kleen wrote: > I think the optimization is a good idea, although i dislike it > that it is complicated for the dynamic markers. If it was just > static it would be much simpler. > Another thing to consider is that there might be hundreds of these probes/tracepoints active in an instrumented kernel. The overhead adds up fast, so the gain may be worth all the pain. - 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/
- Follow-Ups:
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- From: Adrian Bunk <[email protected]>
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- References:
- [patch 00/10] Immediate Values
- From: Mathieu Desnoyers <[email protected]>
- [patch 10/10] Scheduler profiling - Use immediate values
- From: Mathieu Desnoyers <[email protected]>
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- From: Alexey Dobriyan <[email protected]>
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- From: Mathieu Desnoyers <[email protected]>
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- From: Andrew Morton <[email protected]>
- Re: [patch 10/10] Scheduler profiling - Use immediate values
- From: Andi Kleen <[email protected]>
- [patch 00/10] Immediate Values
- Prev by Date: Re: [PATCH] some kmalloc/memset ->kzalloc (tree wide)
- Next by Date: RFC: CONFIG_PAGE_SHIFT (aka software PAGE_SIZE)
- Previous by thread: Re: [patch 10/10] *Tests* Scheduler profiling - Use immediate values
- Next by thread: Re: [patch 10/10] Scheduler profiling - Use immediate values
- Index(es):
 |