Memory Management Learning note

I will always go back and learn about memory management, but I will always learn and forget it. Maybe it is not easy for me to understand programs.

From the Job Manager and process explorer, we often see various memory concepts. What do they mean?

Below I will write a simple colloquial understanding, which may be biased. I will try again later and find the mistake and change it back.

Vitrual memory: this is because every process can see 4 GB memory, and the actual physical memory is not that large. The key is that many processes share the memory, then the operating system will tell the system that the process has 4 GB. however, the actual operating system only gives working set and private bytes physical memory to it. When a process accesses an address that it thinks will be converted by the operating system, if it is accessed in the physical memory, if it is not, it will trigger a page error and the operating system will go to the disk (that is, the windows page file pagefile you set. sys) Find the specified page, load it into the memory, and then let the process access

Workingset: The amount of physical memory that the system allows the process to use. It is processed by the system and mainly used for code running.

Private bytes: memory used by the Process to submit an application. It stores data.

Ws private: records the space exclusive to processes in the workingset.

Ws retriable indicates that these can be shared by other processes, but not shared or already shared.

Ws shared indicates that the file has been shared. Generally, it is a file such as kernel32.dll.

Page faults each process has a working set, that is, the specified number of physical memory. When the accessed memory is not in the physical memory, a page faults is triggered.

12.23.2008 by vivilisa