For each running process, the mapping between virtual and physical address is maintained in a data structure called the page table.
对于每个正在运行的进程，虚拟地址与物理地址之间的映射是在一个称作页表的数据结构中维护的。
It has an integrated memory management unit that is normally used to provide access to the address space of one process by using the same page table lookup as the PPE.
它具有一个集成的内存管理单元，通常使用与PPE类似的页表查询机制来提供对某个进程地址空间的访问。
For every page mapped by each process, page-table entries must also be created to map the virtual address to the physical address.
由于每个页都要由每个进程映射，必须创建页表条目来将虚拟地址映射到物理地址。
In exchange, the process of using these page-table entries is somewhat slower.
作为代价，使用这些页表条目的进程会稍微慢一些。
In such a situation, every process mapping that same 1 GB of memory would consume its own 2 MB worth of page-table entries.
在这种情况下，每个映射到同一块1GB内存的进程将为页表条目付出自己2MB的代价。
However, before they can be swapped out, every single process mapping that page must be found so that the page-table entry for the page in that process can be updated.
不过，在它们可以被交换出去之前，必须找到映射那个页的每一个进程，这样那些进程中相应页的页表条目才可以被更新。
If you have a process that maps 1 GB of memory with 4 KB pages, it would take 262,144 page-table entries to keep track of those pages.
如果您的一个进程要使用4KB的页来映射1GB内存，这将用到262,144个页表条目来保持对那些页的追踪。
If you have a process that maps 1 GB of memory with 4 KB pages, it would take 262,144 page-table entries to keep track of those pages.
如果您的一个进程要使用4KB的页来映射1GB内存，这将用到262,144个页表条目来保持对那些页的追踪。
应用推荐