<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Question on Intel® Xeon® uncore performance counter IIO_CREDITS_REJECT in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/Question-on-Intel-Xeon-uncore-performance-counter-IIO-CREDITS/m-p/1708865#M8561</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am trying to understand peer-to-peer (P2P) transmission behavior on an Intel® Xeon® Scalable processor (Intel® Xeon® Gold 6526Y) using uncore performance counters. I am focusing on the &lt;/SPAN&gt;IIO_CREDITS_REJECT&lt;SPAN&gt; event (&lt;/SPAN&gt;EventCode=0x34&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;According to the &lt;A href="https://www.intel.com/content/www/us/en/content-details/817509/5th-gen-intel-xeon-scalable-processor-xcc-codename-emerald-rapids-uncore-performance-monitoring-guide.html" target="_self"&gt;document&lt;/A&gt; and the &lt;A href="https://github.com/intel/perfmon/blob/main/EMR/events/emeraldrapids_uncore_experimental.json" target="_self"&gt;GitHub repo&lt;/A&gt;, there are 3 documented umasks for this event:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;UMask=0x08 → UNC_M2P_IIO_CREDITS_REJECT.DRS&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;UMask=0x10 → UNC_M2P_IIO_CREDITS_REJECT.NCB&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;UMask=0x20 → UNC_M2P_IIO_CREDITS_REJECT.NCS&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran an application on socket 1 that generates P2P traffic and collected performance counter data with the following command:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ sudo perf stat -a --per-socket \
-e 'uncore_m2pcie_1/event=0x34,umask=0x08/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x10/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x20/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0xff/' \
-- sleep 10

 Performance counter stats for 'system wide':

S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0xff/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S1        1     44,001,744,822      uncore_m2pcie_1/event=0x34,umask=0xff/                                   

      10.000831997 seconds time elapsed&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;I was trying to use umask=0xff to aggregate all sub-events.&lt;/SPAN&gt;&amp;nbsp;After narrowing things down,&amp;nbsp;&lt;SPAN&gt;I found that &lt;/SPAN&gt;umask=0x02&lt;SPAN&gt; alone reproduces the large count:&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ sudo perf stat -a --per-socket \
-e 'uncore_m2pcie_1/event=0x34,umask=0x08/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x10/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x20/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x02/' \
-- sleep 10

 Performance counter stats for 'system wide':

S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x02/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S1        1     44,004,918,932      uncore_m2pcie_1/event=0x34,umask=0x02/                                   

      10.000857627 seconds time elapsed&lt;/LI-CODE&gt;&lt;P&gt;Does the subevent uncore_m2pcie_1/event=0x34,umask=0x02 mean something? Is there any other document related with it?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Aug 2025 04:12:46 GMT</pubDate>
    <dc:creator>k1234</dc:creator>
    <dc:date>2025-08-12T04:12:46Z</dc:date>
    <item>
      <title>Question on Intel® Xeon® uncore performance counter IIO_CREDITS_REJECT</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/Question-on-Intel-Xeon-uncore-performance-counter-IIO-CREDITS/m-p/1708865#M8561</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I am trying to understand peer-to-peer (P2P) transmission behavior on an Intel® Xeon® Scalable processor (Intel® Xeon® Gold 6526Y) using uncore performance counters. I am focusing on the &lt;/SPAN&gt;IIO_CREDITS_REJECT&lt;SPAN&gt; event (&lt;/SPAN&gt;EventCode=0x34&lt;SPAN&gt;).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;According to the &lt;A href="https://www.intel.com/content/www/us/en/content-details/817509/5th-gen-intel-xeon-scalable-processor-xcc-codename-emerald-rapids-uncore-performance-monitoring-guide.html" target="_self"&gt;document&lt;/A&gt; and the &lt;A href="https://github.com/intel/perfmon/blob/main/EMR/events/emeraldrapids_uncore_experimental.json" target="_self"&gt;GitHub repo&lt;/A&gt;, there are 3 documented umasks for this event:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;UMask=0x08 → UNC_M2P_IIO_CREDITS_REJECT.DRS&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;UMask=0x10 → UNC_M2P_IIO_CREDITS_REJECT.NCB&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;UMask=0x20 → UNC_M2P_IIO_CREDITS_REJECT.NCS&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran an application on socket 1 that generates P2P traffic and collected performance counter data with the following command:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ sudo perf stat -a --per-socket \
-e 'uncore_m2pcie_1/event=0x34,umask=0x08/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x10/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x20/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0xff/' \
-- sleep 10

 Performance counter stats for 'system wide':

S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0xff/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S1        1     44,001,744,822      uncore_m2pcie_1/event=0x34,umask=0xff/                                   

      10.000831997 seconds time elapsed&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;I was trying to use umask=0xff to aggregate all sub-events.&lt;/SPAN&gt;&amp;nbsp;After narrowing things down,&amp;nbsp;&lt;SPAN&gt;I found that &lt;/SPAN&gt;umask=0x02&lt;SPAN&gt; alone reproduces the large count:&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ sudo perf stat -a --per-socket \
-e 'uncore_m2pcie_1/event=0x34,umask=0x08/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x10/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x20/' \
-e 'uncore_m2pcie_1/event=0x34,umask=0x02/' \
-- sleep 10

 Performance counter stats for 'system wide':

S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S0        1                  0      uncore_m2pcie_1/event=0x34,umask=0x02/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x08/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x10/                                   
S1        1                  0      uncore_m2pcie_1/event=0x34,umask=0x20/                                   
S1        1     44,004,918,932      uncore_m2pcie_1/event=0x34,umask=0x02/                                   

      10.000857627 seconds time elapsed&lt;/LI-CODE&gt;&lt;P&gt;Does the subevent uncore_m2pcie_1/event=0x34,umask=0x02 mean something? Is there any other document related with it?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Aug 2025 04:12:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/Question-on-Intel-Xeon-uncore-performance-counter-IIO-CREDITS/m-p/1708865#M8561</guid>
      <dc:creator>k1234</dc:creator>
      <dc:date>2025-08-12T04:12:46Z</dc:date>
    </item>
  </channel>
</rss>

