<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory Mapping on Nalar</title>
    <link>https://nalar.dev/tags/memory-mapping/</link>
    <description>Recent content in Memory Mapping on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/memory-mapping/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>MADV_DONTFORK Excludes Memory Ranges from Child Address Spaces</title>
      <link>https://nalar.dev/madv-dontfork-excludes-memory-ranges-from-child-address-spaces/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/madv-dontfork-excludes-memory-ranges-from-child-address-spaces/</guid>
      <description>&lt;p&gt;&lt;code&gt;MADV_DONTFORK&lt;/code&gt; changes a specific part of Linux process creation: a mapping marked with this advice is not made available in the child created by &lt;code&gt;fork()&lt;/code&gt;. The parent keeps the mapping. The child starts without that address range, so an address that was valid there in the parent is not automatically valid in the child.&lt;/p&gt;&#xA;&lt;p&gt;This is a semantic control over mapping inheritance, not a cache hint. It belongs to the Linux-specific &lt;code&gt;madvise()&lt;/code&gt; operations whose effects can change memory behavior.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
