<?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 Re: pqos and CHAs in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/pqos-and-CHAs/m-p/1380449#M8051</link>
    <description>&lt;P&gt;As far as I know, all of Intel's cache allocation control technologies work by restricting the number of "ways" of the cache that can be accessed for a particular QoS class or access type. &amp;nbsp;For example, DMA writes to system memory are cached in 1 or 2 "ways" of the LLC. &amp;nbsp;The mapping of address to CHA slice and to set within the CHA is unchanged, but the cache is effectively direct-mapped or 2-way set associative for those transactions.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Section 17.19.2 of Volume 3 of the Intel Architectures SW Developer's Manual supports this general understanding of how Intel's Cache Allocation Technology works, but notes that the implementation may differ from a simple 1:1 mapping:&lt;/P&gt;
&lt;DIV class="page" title="Page 668"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;It is generally expected that in way-based implementations, one capacity mask bit corresponds to some number of ways in cache, but the specific mapping is implementation-dependent.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 28 Apr 2022 15:15:04 GMT</pubDate>
    <dc:creator>McCalpinJohn</dc:creator>
    <dc:date>2022-04-28T15:15:04Z</dc:date>
    <item>
      <title>pqos and CHAs</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/pqos-and-CHAs/m-p/1380025#M8047</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it possible to modify memory address - CHA affinity via:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.mankier.com/8/pqos" target="_blank"&gt;https://www.mankier.com/8/pqos&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It sounds like this might be possible. If that would be the case, how would pseudorandom Intel hashing function that maps memory addresses to CHAs would change (if it changes at all)?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks and best regards&lt;/P&gt;</description>
      <pubDate>Wed, 27 Apr 2022 08:28:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/pqos-and-CHAs/m-p/1380025#M8047</guid>
      <dc:creator>aozcan</dc:creator>
      <dc:date>2022-04-27T08:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: pqos and CHAs</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/pqos-and-CHAs/m-p/1380449#M8051</link>
      <description>&lt;P&gt;As far as I know, all of Intel's cache allocation control technologies work by restricting the number of "ways" of the cache that can be accessed for a particular QoS class or access type. &amp;nbsp;For example, DMA writes to system memory are cached in 1 or 2 "ways" of the LLC. &amp;nbsp;The mapping of address to CHA slice and to set within the CHA is unchanged, but the cache is effectively direct-mapped or 2-way set associative for those transactions.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Section 17.19.2 of Volume 3 of the Intel Architectures SW Developer's Manual supports this general understanding of how Intel's Cache Allocation Technology works, but notes that the implementation may differ from a simple 1:1 mapping:&lt;/P&gt;
&lt;DIV class="page" title="Page 668"&gt;
&lt;DIV class="layoutArea"&gt;
&lt;DIV class="column"&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;EM&gt;It is generally expected that in way-based implementations, one capacity mask bit corresponds to some number of ways in cache, but the specific mapping is implementation-dependent.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 28 Apr 2022 15:15:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/pqos-and-CHAs/m-p/1380449#M8051</guid>
      <dc:creator>McCalpinJohn</dc:creator>
      <dc:date>2022-04-28T15:15:04Z</dc:date>
    </item>
  </channel>
</rss>

