iMC bypass commands

midhul — Sat, 09 Jul 2022 01:04:13 GMT

Hello,

I am trying to measure iMC performance monitoring counters on a Cascake Lake server. In particular, I am looking at the number of DRAM Activate commands issued by the iMC on a per-channel basis (ACT_COUNT event in section 2.3.7 of Intel Uncore performance monitoring manual: https://kib.kiev.ua/x86docs/Intel/PerfMon/336274-001.pdf)

The ACT_COUNT event has 3 filters (3 umasks):

ACT_COUNT.RD: "Activate due to Read"
ACT_COUNT.WR: "Activate due to Write"
ACT_COUNT.BYP: "Activate due to Bypass"

When I run a simple benchmark performing reads of random cache lines on a single core, a significant fraction of activates (~75%) are of the third type (ACT_COUNT.BYP). I am trying to understand what the third type of activates (ACT_COUNT.BYP) refers to. What is "Bypass"? I see another relevant counter "BYP_CMDS" (Bypass command events), and the description says "ACT command issued by 2 cycle bypass". Does anyone know what this 2 cycle bypass means, and how these are different from normal activates? I had no luck finding anything pertaining to "bypass" in the DRAM literature.

Thanks

Midhul

Re: iMC bypass commands

A_T_Intel — Mon, 24 Oct 2022 15:12:27 GMT

There is an optimized path in the memory controller that may be taken by qualifying reads to reduce latency and these will count as ACT_COUNT.BYP. This only applies to reads, so to get the total read activates you will need ACT_COUNT.BYP + ACT_COUNT.RD.

topic Re: iMC bypass commands in Software Tuning, Performance Optimization & Platform Monitoring

iMC bypass commands

Re: iMC bypass commands