Seeking your suggestion, thank you!
We are still researching the possibilities. However, to do this properly can you provide additional information to clarify? Can you clarify what is meant by coherence as it is referenced in your original post?
Are you using NHM? There is a formula for NUMA distribution on NMH that might be of interest to you. To determine the NUMA distribution for your workload:
% Remote Access =
(OFFCORE_RESPONSE_0.DATA_IN.REMOTE_DRAM / (OFFCORE_RESPONSE_0.DATA_IN.LOCAL_DRAM + OFFCORE_RESPONSE_0.DATA_IN.REMOTE_DRAM)) * 100
The events that are available are listed below. Unfortunately, there are not events for each of the scenarios you have described. However, these events may prove useful in the work you are attempting to accomplish. Detailed information about each of these events can be found in the Intel VTune Amplifier XE 2011 on-line help. To access on-line help, open Intel VTune Amplifier XE 2011 click on Help > Intel VTune Amplifier XE 2011 Help. The on-line help window will appear. Click on the Index tab and enter the event name in the keyword field. The related documentation will display.
Found in requesting cores L1:
- In E state: L1D_CACHE_LD.E_STATE
- In S state: L1D_CACHE_LD.S_STATE
- In M state: L1D_CACHE_LD.M_STATE
Found in requesting cores L2:
- In E state: L2_DATA_RQSTS.DEMAND.E_STATE
- In S State: L2_DATA_RQSTS.DEMAND.S_STATE
- In M state: L2_DATA_RQSTS.DEMAND.M_STATE
Found in shared L3:
- In E or M state: MEM_LOAD_RETIRED.LLC_UNSHARED_HIT
- In S State: not available
Found in sibling cores L2:
- In E, S, or M state: MEM_LOAD_RETIRED.OTHER_CORE_L2_HIT_HITM
Found in locally homed remote L3:
- In E or S state: REMOTE_CACHE_LOCAL_HOME_HIT
- In M state: not available
Found in remotely homed remote L3:
- In E, S, or M state: not available
Let us know if you need additional information or follow-up.