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

Andi,

On Thu, 08 Jun 2006, Andi Kleen wrote:
> 
> > > Originally because it made assembly too unreadable. Later it was discovered
> > > it produces smaller code too.
> > > 

Another quick check on Intel 630.  w/o -fno-reorder-blocks: code increased 2% in
size; performance increased 2% per hyperthread; code still as readable with
objdump -S -d.  Rather marginal one way or the other.

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

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: Problem related to Red Hat Linux kernel 2.6.9-5.EL
Next by Date: Re: [PATCH] limit power budget on spitz
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):
- 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]