Memory management: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content deleted Content added
added image to paging |
fixed layout |
||
| Line 25: | Line 25: | ||
Having an individual virtual-to-physical mapping for each address is of course ineffective. The traditional approach to virtual memory is to split up the available physical memory into chunks (pages), and to map virtual to physical addresses ''page-wise''. This task is largely handled by the [[MMU]], so the performance impact is low, and generally accepted as an appropriate price to pay for memory protection. |
Having an individual virtual-to-physical mapping for each address is of course ineffective. The traditional approach to virtual memory is to split up the available physical memory into chunks (pages), and to map virtual to physical addresses ''page-wise''. This task is largely handled by the [[MMU]], so the performance impact is low, and generally accepted as an appropriate price to pay for memory protection. |
||
[[Image:Virtual memory.png |
[[Image:Virtual memory.png|frame|none|paging illustrated: two process with different views of the same physical memory]] |
||
==Virtual Memory== |
==Virtual Memory== |
||