在高端内存中存储页表条目。
作为代价,使用这些页表条目的进程会稍微慢一些。
In exchange, the process of using these page-table entries is somewhat slower.
表1(在图7中)显示了基于最大分区内存值来分配的页表空间大小。
Table 1 (in Figure 7) shows the size of the page table space allocated based on the maximum partition memory value.
Hypervisor使用全局分区页表将虚拟地址转换为系统范围的物理地址。
The hypervisor converts a virtual address to a system-wide physical address using the global partition page tables.
页表的大小与页面大小成反比,这意味着页面大小越小,页表就越大,开销也就越大。
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.
在这种情况下,每个映射到同一块1GB内存的进程将为页表条目付出自己2MB的代价。
In such a situation, every process mapping that same 1 GB of memory would consume its own 2 MB worth of page-table entries.
Hypervisor可以访问整个内存空间,并且通过全局分区页表来维护分配给分区的内存。
The hypervisor has access to the entire memory space, and maintains the memory allocated to partitions through a global partition page table.
对于每个正在运行的进程,虚拟地址与物理地址之间的映射是在一个称作页表的数据结构中维护的。
For each running process, the mapping between virtual and physical address is maintained in a data structure called the page table.
如果TLB没有命中,那么就需要访问存储在主存中的页表,而这样做需要消耗相当多的处理器周期。
A TLB miss requires accessing a page table that is stored in the main memory, which consumes considerably more processor cycles.
POWER5 +处理器架构(运行AIX 5l操作系统)通过引入多页面大小来解决页表问题。
The POWER5 + processor architecture (running the AIX 5l operating system) addresses the page table problem by introducing multiple page sizes.
在Linux内存管理器中,页表保持对进程使用的内存物理页的追踪,它们将虚拟页映射到物理页。
In the Linux memory manager, page tables keep track of the physical pages of memory that are used by a process, and they map the virtual pages to the physical pages.
然而,如果将它设置的太大,则可能会由于为该分区创建的页表大小而浪费所管理系统上的宝贵内存资源。
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.
它具有一个集成的内存管理单元,通常使用与PPE类似的页表查询机制来提供对某个进程地址空间的访问。
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.
pte链的每一个条目使用4个字节来存储指向页表条目的指针,用另外4个字节来存储指向链的下一个条目的指针。
Each entry in the PTE chain USES 4 bytes to store a pointer to the page-table entry and an additional 4 bytes to store the pointer to the next entry on the chain.
还有一些代码通过使用影子页表(shadow page -table)和管理x86区段来提供内存映射。
There's code to provide the memory mapping through the use of shadow page-tables and management of x86 segments.
不过,在它们可以被交换出去之前,必须找到映射那个页的每一个进程,这样那些进程中相应页的页表条目才可以被更新。
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.
在Linux 2.4内核中,这是一项令人生畏的任务,因为为了确定某个页是否被某个进程映射,必须遍历每个进程的页表。
In the Linux 2.4 kernel, this can be a daunting task as the page tables for every process must be traversed in order to determine whether or not the page is mapped by that process.
如果您的一个进程要使用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.
POWER Hypervisor使用全局分区页表执行虚拟内存管理,并管理分区尝试访问超出其分配限制之外的内存的请求。
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.
假定在前面的中使用页大小为4MB的大内存页,同样1 GB内存只用256个页表条目就可以映射,而不需要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.
操作系统不能直接地访问这个Hypervisor资源,可以使用Hypervisor调用读取全局页表、或者向全局页表写入一个新的条目。
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.
下面的例子定义了两个缓冲池和两个表空间,一个表空间的页宽为4KB,另一个表空间的页宽为32KB(注意,一个表空间总是要有一个缓冲池,且缓冲池要有一个匹配的页宽) 。
The following example defines two buffer pools and two table spaces, one each with 4KB and 32KB pages. (Note that a table space always requires a buffer pool with a matching page size.)
本例中,10%的表数据页用于表统计信息的收集,而对于索引统计信息,将使用所有的索引页。
In this example, 10 percent of table data pages are used for the collection of table statistics, while for index statistics all of the index pages will be used.
如果可以将表放到具有较小页的表空间中,或者可以充分利用较大的页大小,那么最常用的访问方法将确定哪一个更好。
If a table can either be placed into a smaller page size table space or fully utilize a larger page size, then the most frequent method of access determines which one is better.
对于CLI和遗留(legacy)JDBC驱动程序,要使用代码页转换表。
For CLI and legacy JDBC drivers, code page conversion tables are used.
缓冲池是内存中的一块存储区域,用于临时读入和更改数据库页(包含表行或索引项)。
A buffer pool is an area of storage in memory into which database pages (containing table rows or index entries) are temporarily read and changed.
不能将行分割到不同的页,因此具有长行的表需要有合适的页大小。
Rows cannot be split between pages, so tables with long rows require the appropriate page size.
这意味着在搜索的时候行、页或甚至整个表都被锁定。
This means rows, pages, or even whole tables can be locked while a search is being performed.
IDS允许应用程序开发人员将锁放在不同的对象上,如数据库、表、页或行、以及索引。
IDS allows application developers to place locks on different objects, like databases, tables, pages or rows, and indexes.
请注意,缓冲池和表空间的页大小都是8K,两者是相同的。
Note that the page sizes of 8K for the buffer pool and table space are the same.
应用推荐