<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Page Cache on Nalar</title>
    <link>https://nalar.dev/tags/page-cache/</link>
    <description>Recent content in Page Cache on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/page-cache/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Readahead Expands Sequential Page-Cache Reads</title>
      <link>https://nalar.dev/linux-readahead-expands-sequential-page-cache-reads/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/linux-readahead-expands-sequential-page-cache-reads/</guid>
      <description>&lt;p&gt;A buffered file read can cause Linux to fetch more data than the application explicitly requested. The extra I/O is readahead: the kernel populates nearby page-cache folios in anticipation of continued access.&lt;/p&gt;&#xA;&lt;p&gt;This behavior sits between application read size and storage request size. A process may issue modest &lt;code&gt;read()&lt;/code&gt; calls while the kernel submits larger reads to keep later accesses from waiting on storage.&lt;/p&gt;&#xA;&lt;h2 id=&#34;readahead-is-page-cache-speculation&#34;&gt;Readahead is page-cache speculation&lt;/h2&gt;&#xA;&lt;p&gt;Buffered file I/O normally passes through the page cache. When requested file data is absent, the kernel must arrange I/O for that miss. The readahead path can extend that operation across additional folios that are not yet present in the cache.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
