Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- Date: Tue, 12 Aug 2008 09:11:08 +0200
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
- Subject: Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> writes: > Maybe what we are seeing is general bloat in kernel execution paths > due to the growth in complexity? Wouldn't surprise me. Have you considered doing profiles? e.g. just oprofiling the benchmark on the different kernels and see if there's some obvious difference in the CPU consumers? -Andi -- 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: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- From: Christoph Lameter
- Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- References:
- tbench regression on each kernel release from 2.6.22 -> 2.6.28
- From: Christoph Lameter
- Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- From: David Miller
- Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- From: Christoph Lameter
- tbench regression on each kernel release from 2.6.22 -> 2.6.28
- Prev by Date: Re: [2.6.26.*] boot problem (ahci/irq related?)
- Next by Date: Re: [patch 15/19] Filesystem: XFS slab defragmentation
- Previous by thread: Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- Next by thread: Re: tbench regression on each kernel release from 2.6.22 -> 2.6.28
- Index(es):