liveBook · Manning

Page fault

A page fault is an exception or memory-access condition that occurs when a process accesses a virtual-memory page requiring operating-system handling.

How 2 Manning books explain it

Latency

A page fault is a processor-generated exception raised when an accessed virtual memory page is not currently mapped to usable physical memory.

How it is used
Explains lazy virtual-memory allocation, file-backed access, swapping, and the latency costs of page faults.
How deep it goes
Traces the hardware trap, operating-system response, file loading, swapping, and latency trade-offs, but not handler implementation.
Examples
Uses executable sections, a 0x200000 address example, mmap(), file-backed pages, swap, and pinned memory.
What you can do after
Evaluate page-fault latency and choose memory mapping, pinning, or access-pattern strategies for workload constraints.

Read how Latency explains page fault →

Rust in Action: Systems programming concepts and techniques

A page fault is a memory-access condition in which the requested address is unavailable and the required data must be fetched into memory.

How it is used
Explains how operating systems supply unavailable virtual-memory data during ordinary program execution.
How deep it goes
Defines the condition and relates it to swapping and address translation, but stops short of detailing the handler’s implementation.
Examples
Uses missing data in RAM, disk-backed page retrieval, and a CPU terminology taxonomy as concrete illustrations.
What you can do after
Evaluate whether a memory-access event is a recoverable page fault or an illegal-address segmentation fault.

Read how Rust in Action: Systems programming concepts and techniques explains page fault →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.