Paging: Difference between revisions

Jump to navigation Jump to search
11 bytes removed ,  5 years ago
m
Rearranged a few sentences in the beginning and fixed some typos.
[unchecked revision][unchecked revision]
(Table 4-6, chapter 4, section 4.3 of the Intel IA64 and IA32 Architecture's Software Developer's Manual, volume 3 states that it should not necessarily be 0 if PAT is supported.)
m (Rearranged a few sentences in the beginning and fixed some typos.)
Line 1:
[[image:Paging_Structure.gif|right|thumb|600x350px|x86 Paging Structure]]
 
Paging is a system which allows each process to see a full virtual address space, without actually requiring the full amount of physical memory to be available or present. 32-bit x86 processors support 32-bit virtual addresses and 4-GiB virtual address spaces, and current 64-bit processors support 48-bit virtual addressing and 256-TiB virtual address spaces; and. Intel havehas released documentation for a planned extension to 57-bit virtual addressing and 128-PiB virtual address spaces. Paging is a system which allows each process to see a full virtual address spaceCurrently, without actually requiring the full amount of physical memory to be available or present. In fact, current implementations of x86-64 have a limit of between 4 GiB and 256 TiB of physical address space (and an architectural limit of 4 PiB of physical address space).
 
In addition to this, paging introduces the benefit of page-level protection. In this system, user processes can only see and modify data which is paged in on their own address space, providing hardware-based isolation. System pages are also protected from user processes. On the x86-64 architecture, page-level protection now completely supersedes [[Segmentation]] as the memory protection mechanism. On the IA-32 architecture, both paging and segmentation exist, but segmentation is now considered 'legacy'.
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu