Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Myth of the Page Fault: Minor vs Major Faults in Linux

The Myth of the Page Fault: Minor vs Major Faults in Linux Ask most software engineers what happens during a Page Fault , and the textbook answer is immediate: "The requested memory address is missing from RAM, so the operating system suspends the process and reads the page from the hard drive or swap partition." While this describes a Major (Hard) Page Fault , it represents a tiny minority of…

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.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your SVG optimizer silently broke your icon. Here's the one-line check.

Your SVG optimizer silently broke your icon. Here's the one-line check. I spent an afternoon comparing SVG optimizers on a set of 28 real icons from Simple Icons. The sizes looked fine.

  • Optimizer replaced path coordinates with "NaN" string
  • Issue due to handling of arc commands and spacing
  • One-line check using "grep" to detect "NaN"

Kubernetes 1.33: What Really Breaks During an Upgrade and How to Anticipate It

Every cluster operator remembers Kubernetes 1.16 and 1.22: whole API groups disappeared overnight, Helm charts exploded, and kubectl apply started returning no matches for kind .

  • Several changes in Kubernetes 1.33 can break clusters during upgrade
  • Watch feature gates, kubelet default behavior, and aggregated APIService endpoints
  • Comprehensive upgrade plan with Pluto and Kubent recommended

More from Thursday 19 November →