Post created for the publication of a single image (clickable). In my opinion, it is the best way to convey the atmosphere of how the memory is arranged in a computer. I portrayed her at the 3-4 year institute on A4 when explaining the state of affairs to someone. So I liked her then, that he gave himself a promise to draw it in electronic form.
The source in the format of VSD (Microsoft Visio) is in my
DropBox . If there are clarifications, amendments, comments - please under the cat.
The relationship between VAP and VP:
The image is loaded into the virtual memory of the system (VP) once and projected into those virtual address spaces (VAP) in which it is required. An EXE or DLL image is identified by a unique path to the file. Accordingly, if several paths lead to the same file, it is possible to perform multiple loading of the same module. The system has a set of DLLs that are loaded into all programs, such as kernel32.dll and other ...
The relationship between VP and OP:
Physical memory (FP) consists of pages. Any EXE or DLL module occupies a certain number of such pages. When the system loads modules for them, they search for free pages into which the image file is loaded. Modules are projected into virtual memory and loaded into physical memory as needed by the OS. You can also use projection for custom files (also called mapping files).
')
The relationship between OP and iron:
The operating system can, at its discretion, move the pages of physical memory into the paging file and back. When the executable code is accessed from the page located in the paging file, the page is loaded into RAM. If the page has not been accessed for a long time and there is a need for memory, the OS can move the page to the paging file.