Andi, On Thu, 08 Jun 2006, Andi Kleen wrote: > > > performance increased 2% per hyperthread; > > That would surprise me. Most likely you made some measurement error. > Don't think there was an error. Tests performed on STREAMS external modules optimized with profiling data. - 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] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- References:
- [PATCH] use unlikely() for current_kernel_time() loop
- From: Andreas Dilger <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: "Brian F. G. Bidulock" <[email protected]>
- Re: [PATCH] use unlikely() for current_kernel_time() loop
- From: Andi Kleen <[email protected]>
- [PATCH] use unlikely() for current_kernel_time() loop
- Prev by Date: [PATCH] Further alterations for memory barrier document
- Next by Date: Re: 2.6.17-rc6-mm1 -- BUG: possible circular locking deadlock detected!
- Previous by thread: Re: [PATCH] use unlikely() for current_kernel_time() loop
- Next by thread: Re: [PATCH] use unlikely() for current_kernel_time() loop
- Index(es):
 |