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

> performance increased 2% per hyperthread; 

That would surprise me. Most likely you made some measurement error.

I guess it can be a difference if it's used in very hot loops, but then
i would expect a fallthrough path to win. Kernel code very rarely
has hot loops like this.

-Andi

-
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: "Brian F. G. Bidulock" <[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]>

Prev by Date: Re: Problem related to Red Hat Linux kernel 2.6.9-5.EL
Next by Date: Re: 2.6.17-rc5-mm2 link issues on s390
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]