<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NUMA on Nalar</title>
    <link>https://nalar.dev/tags/numa/</link>
    <description>Recent content in NUMA on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/numa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NUMA Makes Memory Location Part of Access Cost</title>
      <link>https://nalar.dev/numa-makes-memory-location-part-of-access-cost/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/numa-makes-memory-location-part-of-access-cost/</guid>
      <description>&lt;h1 id=&#34;numa-makes-memory-location-part-of-access-cost&#34;&gt;NUMA Makes Memory Location Part of Access Cost&lt;/h1&gt;&#xA;&lt;p&gt;A large multiprocessor server can expose one physical address space while giving different processors different paths to that memory. A load from a page attached to the processor running a thread can take a shorter route than a load from memory attached to another processor package or NUMA node.&lt;/p&gt;&#xA;&lt;p&gt;This arrangement is called &lt;strong&gt;non-uniform memory access&lt;/strong&gt;, or NUMA. It lets systems scale memory capacity and bandwidth across multiple processor sockets or chiplet groups without forcing every memory request through one centralized controller.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
