RE: [patch 10/10] Scheduler profiling - Use immediate values

> Also cache misses in this situation tend to be much more than 48
cycles
> (even an K8 with integrated memory controller with fastest DIMMs is
> slower than that)  Mathieu probably measured an L2 miss, not a load
from
> RAM.
> Load from RAM can be hundreds of ns in the worst case.
> 

The 48 cycles sounds to me like a memory load in an unloaded system, but
it is quite low. I wonder how it was measured...

  tong
-
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 10/10] *Tests* Scheduler profiling - Use immediate values
    • From: Mathieu Desnoyers <[email protected]>
  • Re: [patch 10/10] Scheduler profiling - Use immediate values
    • From: Andi Kleen <[email protected]>

• References:
  • Re: [patch 10/10] Scheduler profiling - Use immediate values
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: kgdb Bad IO access
• Next by Date: Re: [2.6 patch] mm/migrate.c: cleanups
• Previous by thread: Re: [patch 10/10] Scheduler profiling - Use immediate values
• Next by thread: Re: [patch 10/10] Scheduler profiling - Use immediate values
• 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]