It's still broken in 17-rc1 ... will send you a patch in a sec.I already have kconfigdebug-set-debug_mutex-to-off-by-default.patch queued up.
OK. That explains why -mm2 bounced back at the end of this graph: http://test.kernel.org/perf/reaim.moe.png But ... it's still way below what 2.6.15 was. There's another thunk down between 2.6.16 and 2.6.16-git18, AFAICS. M. - 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: Clear performance regression on reaim7 in 2.6.15-git6
- From: "Martin J. Bligh" <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- References:
- Clear performance regression on reaim7 in 2.6.15-git6
- From: "Martin J. Bligh" <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- From: Andrew Morton <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- From: "Martin J. Bligh" <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- From: Andrew Morton <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- From: "Martin J. Bligh" <[email protected]>
- Re: Clear performance regression on reaim7 in 2.6.15-git6
- From: Andrew Morton <[email protected]>
- Clear performance regression on reaim7 in 2.6.15-git6
- Prev by Date: Re: Clear performance regression on reaim7 in 2.6.15-git6
- Next by Date: Re: [patch] ipv4: initialize arp_tbl rw lock
- Previous by thread: Re: Clear performance regression on reaim7 in 2.6.15-git6
- Next by thread: Re: Clear performance regression on reaim7 in 2.6.15-git6
- Index(es):
 |