The article says, in the lead:
In computer operating systems, memory paging is a memory management scheme that allows the physical memory used by a program to be non-contiguous.[1] This also helps avoid the problem of memory fragmentation and requiring compaction to reduce fragmentation.
Paging is often combined with the related technique of allocating and freeing page frames and storing pages on and retrieving them from secondary storage[a] in order to allow the aggregate size of the address spaces to exceed the physical memory of the system.[2] For historical reasons, this technique is sometimes referred to as swapping.
When combined with virtual memory, it is known as paged virtual memory.
In this scheme, the operating system retrieves data from secondary storage in blocks of the same size (pages).
Paging is an important part of virtual memory implementations in modern operating systems, using secondary storage to let programs exceed the size of available physical memory.
However, much - most? - of the rest of the article appears to be discussing paged virtual memory. Memory paging § Page faults, Memory paging § Page fetching techniques, Memory paging § Page replacement techniques, Memory paging § Thrashing, most if not all of the subsections of Memory paging § Implementations, Memory paging § Performance, and at least some of Memory paging § Physical and virtual address space sizes are specifically discussing paged virtual memory.
Perhaps either most of what's here should be merged into Virtual memory § Paged virtual memory, or a new "Paged virtual memory" page hold all but a summary of paged VM, with Virtual memory § Paged virtual memory holding that summary and pointing to said page as the main article. Guy Harris (talk) 01:21, 20 August 2025 (UTC)
