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

> I found that memory latency is difficult to measure in modern x86
> CPUs because they have very clever prefetchers that can often
> outwit benchmarks.

A pointer-chasing program that accesses a random sequence of addresses
usually can produce a good estimate on memory latency. Also, prefetching
can be turned off in BIOS or by modifying the MSRs.
 
> Another trap on P4 is that RDTSC is actually quite slow and
synchronizes
> the CPU; that can add large measurement errors.
> 
> -Andi

The cost can be amortized if the portion of memory accesses is long
enough.

  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] Scheduler profiling - Use immediate values
    • From: Mathieu Desnoyers <[email protected]>

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

• Prev by Date: Re: [RFC][PATCH] introduce panic_gently
• Next by Date: Re: [PATCH] slub: don't export static kmem_cache_open
• 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]