Will memory mapped IO reduce the memory I can "see"?
将内存映射IO减少内存我可以“看到”？
Other devices are not memory mapped on the processor bus.
其他的设备没有被映射到处理机总线上。
Segments 3-C and E: Memory mapped regions (including files) and shared memory
分段 3-C和E：内存映射区域（包括文件）和共享内存
This will create the memory mapped file but to start using it we will need a map view.
这样，我们就创建了一个内存映射文件。
With the stream in place, we can now create the memory mapped file. Let's see an example.
创建合适的流之后，现在就可以创建内存映射文件了。
Performance counters use a memory mapped file, or Shared memory, to publish performance data.
性能计数器使用内存映射文件或共享内存发布性能数据。
Now, there is a small drawback with this approach and is related to the size of the memory mapped file.
但是这种方法有个小小的缺点，这和内存映射文件的大小有关。如果事先不知道大小的话，为了以防万一，你可能会构造一个超级大的文件。
Here I am using two different instances of same application to read write data from memory mapped file.
在这里我用两个相同的应用程序的不同实例来读写数据从内存映射文件。
The physical memory that is mapped for the guest operating system is actually virtual memory mapped into the process.
映射给客户操作系统的物理内存实际上是映射给这个进程的虚拟内存。
If we explore the construction of the memory mapped file we can see that there is no stream, we just name the resource.
如果我们想要探究内存映射文件结构的话，不需要构造一个流，只要找到该资源的名字即可。
These include convenience methods for reading and writing text-based files, significantly faster directory enumeration, and support for memory mapped files.
包括读写文本文件的便捷方法，快速地列举目录，对内存映射文件的支持。
Finally, another interesting area is the creation of multiple map views, these can work on the same memory mapped file accessing different areas of the files.
最后，让我们来看一下另外一个有意思的领域：创建多个映射视图。它们同时工作访问同一个内存映射文件的不同区域。
The access to the file USES the same syntax as the previous example, remember that if you close the memory mapped file this will be non accessible, this issue catches many developer.
如何访问文件就跟前述的示例一样了。千万记住，如果你关闭了内存映射文件，那么它就不能访问了。
Now if we want to read from it, the other process needs also to create a memory mapped file, we can use the other static initialize that opens an existing one or creates one if it does not exist.
其它进程如何读取该内存映射文件的内容呢。 一样，我们先创建一个内存映射文件。
Remember the system break, the location that is the edge of mapped memory for the process?
还记得系统中断点吗？该位置是进程映射的内存边界。
As mentioned above, the edge of mapped memory — last valid address — is often known as the system break or the current break.
如前所述，被映射的内存的边界(最后一个有效地址)常被称为系统中断点或者当前中断点。
This value also includes the pages to or from non-cached mapped memory files.
该值还包括往返于非缓存、映射后的内存文件的页面。
When an application references a page that is not mapped into real memory, the system generates a page fault.
如果应用程序引用了某个分页，而该分页并没有映射到实际内存中，那么系统将产生一个缺页。
So, in the above example, there are 16529 non-computational file pages mapped into memory.
因此，在上面的示例中，一共有16529个非计算性的文件分页被映射到了内存中。
As the name implies, a memory-mapped file maps a file-like construct to an address in memory.
顾名思义，一个内存映射文件将一个类似文件的结构映射到内存的地址中。
With the next version of the BCL,.net developers will be able to use memory-mapped files directly instead of via platform invoke calls.
在BCL的下一个版本中，. NET开发人员将能够直接使用内存映射文件，而无需通过平台调用的方式。
The ppe does this through memory-mapped register access from kernel mode, while the SPE writes to its DMA channels from code running on the SPU.
PPE可以通过在内核模式中使用内存映射寄存器来发起dma传输，而SPE则可以使用在SPU上运行的代码来写入dma通道。
Then, when it is time to start the JVM, instead of loading the system classes from scratch, the memory-mapped files are loaded.
这样，在启动J VM时，就不会从头开始装入系统类，而是装入内存映射文件。
Inuse-number of 4k pages mapped into memory.
inuse——映射到内存中的4K分页的数目。
So, in the above example, there are 188426 working storage pages mapped into memory.
因此，在上面的示例中，一共有188426个工作存储分页映射到内存中。
pin—number of 4K pages mapped into memory and pinned (pin is a subset of inuse)
pin ——映射到内存中的、且固定的4K分页的数目（pin是inuse 的子集）
I'll discuss an eighth type, MappedByteBuffer, available for memory-mapped files, later in this article.
在本文后面，我将讨论第8种类型MappedByteBuffer，它用于内存映射文件。
High performance (SendFile API support and memory-mapped files).
高性能(支持SendFileAPI和内存映射文件)。
In the DB2 implementation of memory Windows, each instance is mapped to an individual memory window.
在内存窗的DB 2实现中，每个实例都被映射到一个单独的内存窗。
In the DB2 implementation of memory Windows, each instance is mapped to an individual memory window.
在内存窗的DB 2实现中，每个实例都被映射到一个单独的内存窗。
应用推荐