图1说明了进程地址空间中的虚拟页如何映射到内存中的物理页帧。
Figure 1 illustrates how virtual pages in a process's address space are mapped to physical page frames in memory.
有些密切的力学如何创建虚拟页映射当MMU页面错误的信号。
Somewhat close in its mechanics to how virtual page mapping is created when MMU signals a page fault.
主要有单一连续存储管理、固定分区管理、页式管理和虚拟页式管理。
Mainly for a single storage management, fixed regional management, page-style management and virtual page-style management.
在2.6内核中，支持两种虚拟页大小：传统的4K b页大小以及16MB页大小。
In the 2.6 kernel, there will be support for two virtual page sizes: the traditional 4kb page size and the 16mb page size.
Linux内核工作于虚拟内存模式：每一个虚拟页对应一个相应的系统内存的物理页。
The Linux kernel operates in a virtual memory mode: for every virtual page there is a corresponding physical page of memory in the system.
Windows通过将来自不同地址空间的多个虚拟页映射到同一个物理地址来实现这种机制。
Windows does this by mapping multiple virtual pages from different address Spaces to the same physical location.
在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.
对于一个特定的虚拟页，根据一条页表记录可以找到对应的物理页，或者是页无法找到的提示(说明存在一个页错误)。
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).
在实验的过程中，相应采用了一些技术：数据的高活跃存储区域和虚拟页技术，这使得系统运行效率得到了提高。
Some techniques in this experiment, such as high-activeness data field technology and Virtual page technology, proves to be more efficient in the system.
虚拟内存到物理内存的映射通过页表完成，这是在底层软件中实现的(见图1)。
The mapping of virtual memory to physical memory occurs through page tables, which are implemented in the underlying hardware (see Figure 1).
内核地址空间中的第一页虚拟内存可通过内核代码访问，但是被标记为只读。
The first page of virtual memory in the kernel address space can be accessed by kernel code, but is marked as read-only.
由于每个页都要由每个进程映射，必须创建页表条目来将虚拟地址映射到物理地址。
For every page mapped by each process, page-table entries must also be created to map the virtual address to the physical address.
对于每个正在运行的进程，虚拟地址与物理地址之间的映射是在一个称作页表的数据结构中维护的。
For each running process, the mapping between virtual and physical address is maintained in a data structure called the page table.
页表的数量与虚拟地址空间的大小成比例。
The number of page table entries is proportional to the size of virtual address space.
将此页放到虚拟目录中并用浏览器打开此页，添加一些角色。
Put this page in your virtual directory and point your browser at it so that you can add some roles.
为了提高效率，如果由硬件管理虚拟内存，内存是按照所谓的内存页方式进行管理的(对于大部分体系结构来说都是4kb)。
For efficiency, given the way that the hardware manages virtual memory, memory is managed in what are called pages (4kb in size for most architectures).
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.
Hypervisor使用全局分区页表将虚拟地址转换为系统范围的物理地址。
The hypervisor converts a virtual address to a system-wide physical address using the global partition page tables.
这种分页算法可以确定对当前位于RAM中的哪些虚拟内存页面的页帧进行回收，并放回到空闲列表中。
This paging algorithm determines which virtual memory pages currently in ram ultimately have their page frames brought back to the free list.
VMM 提供了一种页面置换算法，该算法用于分配页帧，以及确定应该将当前RAM 中的哪些虚拟内存页面的页帧置换回空闲列表。
The VMM has a page-replacement algorithm, which assigns the page frames and determines exactly which virtual-memory pages currently in RAM will have their page frames brought back to the free list.
虚拟区可以通过数据库服务器得到较大扩展，并且可以通过操作系统将虚拟区页移出(page out)磁盘。
The virtual portion is quite expandable by the database server and can be paged out to disk by the operating system.
每个操作系统进程占用自己的虚拟地址空间，即一组可以读写的虚拟内存页。
Each operating-system process is allocated its own virtual address space — a set of virtual-memory pages that it can read from and write to. Each page can be in one of three states.
Windows所使用的现代虚拟内存实现中，虚拟存储被组织成大小相同的单位，称为页。
In the modern implementation of virtual memory that Windows USES, virtual storage is organized into equal-sized units known as pages.
由于大部分进程的虚拟地址空间大而散，页表入口只能定位在实际使用的那部分地址空间上。
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.
为了能同时对虚拟地址空间和它对应的页表都进行分页。
So we can page the virtual address space AND page the page table.
如何知道哪些页面的内核，在虚拟地址空间对应于一个换出的物理页帧？
How does kernel know, which pages in the virtual address space correspond to a swapped out physical page frame?
为了找到指定虚拟地址所对应的物理地址，必须定位于合适的页表及其中正确的入口。
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.
表项包含真正内存地址的页的虚拟地址，它包括拥有这个页的进程的信息。
Entry consists of the virtual address of the page stored in that real memory location, with information about the process that owns that page.
这些虚拟地址映射到物理内存页表，这是维护操作系统的内核和处理器咨询。
These virtual addresses are mapped to physical memory by page tables, which are maintained by the operating system kernel and consulted by the processor.
用户登录并拥有个人资料页，可以上传自己的个人图片，或者虚拟人物。
Users log in and have a profile page, can upload their profile picture or use an avatar.
应用推荐