<?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>Troy's Blog</title><link>https://blog.troy-y.org/</link><description>Recent content on Troy's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 23 Apr 2026 18:15:51 +0800</lastBuildDate><atom:link href="https://blog.troy-y.org/index.xml" rel="self" type="application/rss+xml"/><item><title>linux-mm[0]: Physical Memory and struct page</title><link>https://blog.troy-y.org/posts/linux-mm-0-physical-memory-and-struct-page/</link><pubDate>Thu, 23 Apr 2026 18:15:51 +0800</pubDate><guid>https://blog.troy-y.org/posts/linux-mm-0-physical-memory-and-struct-page/</guid><description>&lt;h2 id="what-is-physical-memory"&gt;What Is Physical Memory?&lt;/h2&gt;
&lt;p&gt;When we talk about memory management in the Linux kernel, the first question to answer is deceptively simple: what &lt;em&gt;is&lt;/em&gt; physical memory, from the kernel&amp;rsquo;s perspective?&lt;/p&gt;
&lt;p&gt;Your RAM is a flat array of bytes. The kernel doesn&amp;rsquo;t treat it as one giant blob — it slices it into fixed-size chunks called &lt;strong&gt;pages&lt;/strong&gt;. On x86_64, the default page size is &lt;strong&gt;4KB&lt;/strong&gt;, and a machine with 8GB of RAM has roughly 2 million of them.&lt;/p&gt;</description></item><item><title>Hello World</title><link>https://blog.troy-y.org/posts/hello-world/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.troy-y.org/posts/hello-world/</guid><description>&lt;p&gt;This is my first Hugo blog post.&lt;/p&gt;
&lt;p&gt;Migrated from Hexo + Butterfly to Hugo + PaperMod, pursuing simplicity and efficiency.&lt;/p&gt;</description></item></channel></rss>