How different in management page table entries (PTE) in kernel space and user space?
如何在管理不同的页表项(pte)在内核空间和用户空间？
Permitted operations are specified using control bits associated with each page table entry.
能允许的操作须指定使用与每个页表入口关联的控制位。
The global partition page table consists of the mapping of PMBs to the LMBs of different partitions.
全局分区页表由不同分区的pmb到lmb的映射组成。
The first translation table is called the Page Directory, and the second is called the Page table.
第一步转换的表称为页目录，第二步的表称为页表。
Switching back and forth between kernel and user space execution does not require a page table swap.
在内核空间和用户空间之间来回切换根本无需切换页表。
Table 1 (in Figure 7) shows the size of the page table space allocated based on the maximum partition memory value.
表1(在图7中)显示了基于最大分区内存值来分配的页表空间大小。
Locking TLB entries can ensure that a memory access to a given region never incurs the penalty of a page table walk.
锁定TLB输入能确保对于给出区域的内存读取绝不会导致页表移动的掉失。
A TLB miss requires accessing a page table that is stored in the main memory, which consumes considerably more processor cycles.
如果TLB没有命中，那么就需要访问存储在主存中的页表，而这样做需要消耗相当多的处理器周期。
From Operating System theory, OS implements a page table entry, PTE, to describe a mapping of a page in VAS to physical page.
来自操作系统的理论，操作系统引入一个页表项，PTE，描述了一个在VAS中的页到物理页的映射。
For each running process, the mapping between virtual and physical address is maintained in a data structure called the page table.
对于每个正在运行的进程，虚拟地址与物理地址之间的映射是在一个称作页表的数据结构中维护的。
The hypervisor has access to the entire memory space, and maintains the memory allocated to partitions through a global partition page table.
Hypervisor可以访问整个内存空间，并且通过全局分区页表来维护分配给分区的内存。
The POWER5 + processor architecture (running the AIX 5l operating system) addresses the page table problem by introducing multiple page sizes.
POWER5 +处理器架构(运行AIX 5l操作系统)通过引入多页面大小来解决页表问题。
The first level MMU entry may contain an invalid entry or it contains a 2nd level page table address that gives a bus error when accessed.
第一级MMU条目可能包含一个无效的条目或它包含了2 第二级页表的访问时，给出了一个的总线错误的地址。
The operating system cannot access this hypervisor resource directly, and USES hypervisor calls to read or write a new entry to the global page table.
操作系统不能直接地访问这个Hypervisor资源，可以使用Hypervisor调用读取全局页表、或者向全局页表写入一个新的条目。
For a particular virtual page, a page table entry will give a corresponding physical page or note that the page is not present (indicating a page fault).
对于一个特定的虚拟页，根据一条页表记录可以找到对应的物理页，或者是页无法找到的提示(说明存在一个页错误)。
The addressed page is not present in memory, the corresponding page Table entry is null, or a violation of the paging protection mechanism has occurred.
寻址的页不在内存中，对应的页表条目是空的，或者是违背了页式管理的保护机制。
Page table copy means that LAHF copies the page table content in kernel mode of the operating system to a set of private page tables it has established.
页表复制指的是LAHF将操作系统内核态页表的内容复制到自己建立的一套私有页表中。
However, if you make it too large, you can waste valuable memory resources on your managed system due to the size of the page table created for the partition.
然而，如果将它设置的太大，则可能会由于为该分区创建的页表大小而浪费所管理系统上的宝贵内存资源。
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类似的页表查询机制来提供对某个进程地址空间的访问。
The size of the page table is inversely proportional to the page size, which implies that the smaller the page size, the larger the page table, and hence more overhead.
页表的大小与页面大小成反比，这意味着页面大小越小，页表就越大，开销也就越大。
To determine the physical address corresponding to a given virtual address, the appropriate page table, and the correct entry within that page table must be located.
为了找到指定虚拟地址所对应的物理地址，必须定位于合适的页表及其中正确的入口。
The POWER Hypervisor performs virtual memory management using a global partition page table, and manages any attempt by a partition to access memory outside its allocated limit.
POWER Hypervisor使用全局分区页表执行虚拟内存管理，并管理分区尝试访问超出其分配限制之外的内存的请求。
While page table fraud means to deceive the operating system that it has found the actual physical address, which is actually not, by modifying the page table in kernel mode.
页表欺骗是通过修改操作系统内核态页表的方法使操作系统以为找到了实际的物理地址，实际上该地址不是真正的物理地址。
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.
由于大部分进程的虚拟地址空间大而散，页表入口只能定位在实际使用的那部分地址空间上。
From the pile of books on your bedside table to your well-organized shelves, whether we notice it or not, our book collections are telling a story before a single page has been turned.
不管我们是否注意到，从床头柜上的一堆书到整齐有序的书架，在翻开一页书之前，我们的藏书就在讲述着一个故事。
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.
不过，在它们可以被交换出去之前，必须找到映射那个页的每一个进程，这样那些进程中相应页的页表条目才可以被更新。
For every page mapped by each process, page-table entries must also be created to map the virtual address to the physical address.
由于每个页都要由每个进程映射，必须创建页表条目来将虚拟地址映射到物理地址。
In this case, I use the PHP code to create a series of tags-one for each page in the table.
在本例中，我使用PHP代码创建了一系列标记—一个标记用于表格中的一个页面。
This means that DB2 fetches every data page in the table space sequentially into the buffer pool.
这意味着DB2按顺序在表空间上提取每一个数据页面到缓冲池。
This means that DB2 fetches every data page in the table space sequentially into the buffer pool.
这意味着DB2按顺序在表空间上提取每一个数据页面到缓冲池。
应用推荐