Re: [PATCH] use unlikely() for current_kernel_time() loop

Andi,

On Thu, 08 Jun 2006, Andi Kleen wrote:
> > 
> > Don't think there was an error.  Tests performed on STREAMS external
> > modules optimized with profiling data.
> 
> You mean with compiler profile feedback? 

No, hand optimized from oprofile runs.

> If that is slower then it would sound like a compiler bug.

What slower?  It was 2% faster.    And that was only the external
kernel modules compiled without the -fno-redorder-blocks flag.

--brian
-
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/

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]>

Prev by Date: Re: mutex vs. local irqs (Was: 2.6.18 -mm merge plans)
Next by Date: Re: IRQ sharing: BUG: spinlock lockup on CPU#0
Previous by thread: Re: [PATCH] use unlikely() for current_kernel_time() loop
Next by thread: [PATCH -mm] Fix return value of delayacct_add_tsk()
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]