<?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 &amp;quot;Cache line splits&amp;quot; are the in Software Tuning, Performance Optimization &amp; Platform Monitoring</title>
    <link>https://community.intel.com/t5/Software-Tuning-Performance/What-is-a-cache-line-boundary/m-p/1144181#M6723</link>
    <description>&lt;P&gt;"Cache line splits" are the first scenario: You are loading or write a data elements where some part of the data is one cache line and the remaining part is in the adjacent cache line.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;On Intel architecture, cache lines are 64B. Cache lines therefore start at a multiple of 64. So, in your example, it would be rather that 0x200 is one cache line and 0x0240 is the next cache line. If you read a DWORD from 0x23f, you have a cache line split.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Please note that, if all your data is aligned, you don't have cache line splits.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Jun 2018 14:44:04 GMT</pubDate>
    <dc:creator>Thomas_W_Intel</dc:creator>
    <dc:date>2018-06-21T14:44:04Z</dc:date>
    <item>
      <title>What is a cache line boundary?</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/What-is-a-cache-line-boundary/m-p/1144180#M6722</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;I have been reading the Intel developer manual (https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf) lately and have come across the term cacheline boundaries mentioned in the AVX section.&lt;/P&gt;

&lt;P&gt;However, I am unsure what exactly a cacheline boundary means?&lt;/P&gt;

&lt;P&gt;Does it mean the point where consecutive memory addresses get split across caches? For instance if address 200 in L1 and address 201 was in L2, accessing an 4 bytes starting from 200 would be a cache line boundary access?&lt;/P&gt;

&lt;P&gt;OR&lt;/P&gt;

&lt;P&gt;Does it mean alignment basically? That is when a cache's well defined boundaries per data element (such as a word or quadword) for every few fixed number of bytes are crossed?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 14:20:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/What-is-a-cache-line-boundary/m-p/1144180#M6722</guid>
      <dc:creator>Aketh_T_1</dc:creator>
      <dc:date>2018-06-21T14:20:56Z</dc:date>
    </item>
    <item>
      <title>"Cache line splits" are the</title>
      <link>https://community.intel.com/t5/Software-Tuning-Performance/What-is-a-cache-line-boundary/m-p/1144181#M6723</link>
      <description>&lt;P&gt;"Cache line splits" are the first scenario: You are loading or write a data elements where some part of the data is one cache line and the remaining part is in the adjacent cache line.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;On Intel architecture, cache lines are 64B. Cache lines therefore start at a multiple of 64. So, in your example, it would be rather that 0x200 is one cache line and 0x0240 is the next cache line. If you read a DWORD from 0x23f, you have a cache line split.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Please note that, if all your data is aligned, you don't have cache line splits.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 14:44:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Tuning-Performance/What-is-a-cache-line-boundary/m-p/1144181#M6723</guid>
      <dc:creator>Thomas_W_Intel</dc:creator>
      <dc:date>2018-06-21T14:44:04Z</dc:date>
    </item>
  </channel>
</rss>

