Storing page-table entries in high memory.
在高端内存中存储页表条目。
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的代价。
For every page mapped by each process, page-table entries must also be created to map the virtual address to the physical address.
由于每个页都要由每个进程映射，必须创建页表条目来将虚拟地址映射到物理地址。
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个页表条目来保持对那些页的追踪。
Assuming a large page size of 4 MB is used in the same example from above, that same 1 GB of memory could be mapped with only 256 page-table entries instead of 262,144.
假定在前面的中使用页大小为4MB的大内存页，同样1GB内存只用256个页表条目就可以映射，而不需要262,144个。
The size of the table (number of entries per page) and data refresh rates can also be changed to meet the your needs.
还可以修改表的大小（每个页面上的条目数量）和数据刷新频率以满足自己的需要。
Then, select the HR.EMPLOYEEPAYINFO and click the Pair iconPair table mapping entries in the upper right-hand corner of the page to pair the two tables.
然后，选择HR.EMPLOYEEPAYINFO并单击该页面右上角的Pair 图标Pair表映射条目 ，将这两个表配对。
Because the virtual address Spaces of most processes are both large and sparse, page table entries are only allocated for the portions of the address space that are actually used.
由于大部分进程的虚拟地址空间大而散，页表入口只能定位在实际使用的那部分地址空间上。
How different in management page table entries (PTE) in kernel space and user space?
如何在管理不同的页表项(pte)在内核空间和用户空间？
Locking TLB entries can ensure that a memory access to a given region never incurs the penalty of a page table walk.
锁定TLB输入能确保对于给出区域的内存读取绝不会导致页表移动的掉失。
Locking TLB entries can ensure that a memory access to a given region never incurs the penalty of a page table walk.
锁定TLB输入能确保对于给出区域的内存读取绝不会导致页表移动的掉失。
应用推荐