Page fault
This article includes a list of general references, but it lacks sufficient corresponding inline citations. (February 2008) |
In computing, a page fault (sometimes called PF or hard fault)
Valid page faults are common and necessary to increase the amount of memory available to programs in any operating system that uses
Types
Minor
If the page is loaded in memory at the time the fault is generated, but is not marked in the
The page could also have been removed from the working set of a process, but not yet written to disk or erased, such as in operating systems that use Secondary Page Caching. For example, OpenVMS may remove a page that does not need to be written to disk (if it has remained unchanged since it was last read from disk, for example) and place it on a Free Page List if the working set is deemed too large. However, the page contents are not overwritten until the page is assigned elsewhere, meaning it is still available if it is referenced by the original process before being allocated. Since these faults do not involve disk latency, they are faster and less expensive than major page faults.
Major
This is the mechanism used by an operating system to increase the amount of program memory available on demand. The operating system delays loading parts of the program from disk until the program attempts to use it and the page fault is generated. If the page is not loaded in memory at the time of the fault, then it is called a major or hard page fault. The page fault handler in the OS needs to find a free location: either a free page in memory, or a non-free page in memory. This latter might be used by another process, in which case the OS needs to write out the data in that page (if it has not been written out since it was last modified) and mark that page as not being loaded in memory in its process page table. Once the space has been made available, the OS can read the data for the new page into memory, add an entry to its location in the memory management unit, and indicate that the page is loaded. Thus major faults are more expensive than minor faults and add storage access latency to the interrupted program's execution.
Invalid
If a page fault occurs for a reference to an address that is not part of the virtual
Invalid conditions
Illegal accesses and invalid page faults can result in a segmentation fault or bus error, resulting in an app or OS crash. Software bugs are often the causes of these problems, but hardware memory errors, such as those caused by overclocking, may corrupt pointers and cause valid code to fail.
Operating systems provide differing mechanisms for reporting page fault errors.
Performance impact
Page faults degrade system performance and can cause
Performance
A larger physical memory also reduces page faults.
See also
Notes
- ^ Microsoft uses the term "hard fault" in some versions of its Resource Monitor, e.g., in Windows Vista (as used in the Resource View Help in Microsoft operating systems).
References
- ISBN 0-596-00565-2. Retrieved 9 October 2021.
- John L. Hennessy, David A. Patterson, Computer Architecture, A Quantitative Approach (ISBN 1-55860-724-2)
- Tanenbaum, Andrew S. Operating Systems: Design and Implementation (Second Edition). New Jersey: Prentice-Hall 1997.
- Intel Architecture Software Developer's Manual–Volume 3: System Programming
External links
- "So What Is A Page Fault?(subscription required)" from OSR Online (a Windows-specific explanation)
- "Virtual Memory Details" from the Red Hat website.
- "UnhandledExceptionFilter (Windows)" from MSDN Online.
- "Page fault overhead" for information about how page faults can crucially affect processing time.