<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Page Cache on Sanketh's Blog</title><link>https://sankethbk.github.io/blog/tags/page-cache/</link><description>Recent content in Page Cache on Sanketh's Blog</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Sun, 05 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sankethbk.github.io/blog/tags/page-cache/index.xml" rel="self" type="application/rss+xml"/><item><title>The Page Cache and Page Writeback</title><link>https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-07-05-page-cache/</link><pubDate>Sun, 05 Jul 2026 00:00:00 +0000</pubDate><guid>https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-07-05-page-cache/</guid><description>&lt;h2 id="the-linux-page-cache--page-writeback"&gt;The Linux Page Cache &amp;amp; Page Writeback&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;The Core Concept:&lt;/strong&gt; Disk access is measured in milliseconds; RAM access is measured in nanoseconds. To bridge this massive performance gap, Linux dynamically uses free physical RAM to cache blocks of disk data.&lt;/p&gt;
&lt;p&gt;This relies on &lt;strong&gt;temporal locality&lt;/strong&gt;: the computing principle that if data is accessed once, it is highly likely to be accessed again very soon.&lt;/p&gt;
&lt;h3 id="1-reading-from-disk"&gt;1. Reading from Disk&lt;/h3&gt;
&lt;p&gt;The cache is granular; Linux caches specific pages of files based on what you actually access, not whole files by default.&lt;/p&gt;</description></item></channel></rss>