{
  "id": 20749802,
  "title": "The Myth of the Page Fault: Minor vs Major Faults in Linux",
  "url": "https://urgent.news/2026/11/19/the-myth-of-the-page-fault-minor-vs-major-faults-in-linux",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-19T13:09:28.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/binarydose/the-myth-of-the-page-fault-minor-vs-major-faults-in-linux-4k16"
  },
  "original_language": "en",
  "account": null,
  "summary": "The article \"The Myth of the Page Fault: Minor vs Major Faults in Linux\" explains the differences between Minor and Major page faults in Linux systems. While many software engineers associate page faults with disk I/O and consider them a major issue, the reality is that over 95% of page faults in production Linux systems are minor faults, which do not involve disk I/O. A minor page fault occurs when the required physical page is already present in RAM, but the process's page table has not yet been linked to it. Common scenarios include shared libraries, the page cache, and anonymous zero-fill on demand. In contrast, major page faults only occur when the page is completely absent from RAM and must be retrieved from persistent storage, resulting in higher costs in terms of CPU cycles and time.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}