The shared-memory header contains a description of all other structures in Shared memory, including internal tables and the buffer pool.
共享内存头包含共享内存中所有其他结构的描述，包括内部表和缓冲池。
When a virtual processor first attaches to Shared memory, it reads address information in the shared-memory header for directions to all other structures.
当一个虚拟进程首次附加到共享内存中时，它读取共享内存头中的地址信息，获取指向其他所有结构的方向。
Shared memory provides the fastest method of interprocess communication, because it processes read and write messages at the speed of memory transfers.
共享内存提供了最快的进程间通信方法，因为它以内存传输的速度来处理读写消息。
There is one database Shared memory set per database.
每个数据库有一个数据库共享内存集。
Its constructor creates the Shared memory and objects in it.
它的构造函数创建共享内存及其中的对象。
Limit: In this configuration, the limit for database Shared memory is 2gb, or 8 segments.
限制：在此配置中，对于数据库共享内存的限制是2gb或8个段。
Application group Shared memory set is not listed because it is allocated from the database Shared memory set.
应用程序组共享内存集没有列出，因为它是从数据库共享内存集中分配的。
So far we have discussed the instance Shared memory, the database Shared memory, the application group Shared memory and the agent private memory.
至此，我们已经讨论了实例共享内存、数据库共享内存和应用程序组共享内存以及代理私有内存。
This class stores the Shared memory identifier.
这个类存储共享内存标识符。
This effectively frees up one segment for database Shared memory.
这将有效地为数据库共享内存一个段。
Since the end address of the instance Shared memory is not fixed, the starting address for the database Shared memory is not fixed either.
因为实例共享内存的结束地址不固定，所以数据库共享内存的起始地址也是不固定的。
This is well under the 1.75gb Shared memory limit, and each database Shared memory segment can safely map contiguously to a quadrant.
这低于1.75GB的共享内存限制，并且每个数据库共享内存段可以安全地连续映射到一个象限。
Note this amount includes both the instance Shared memory and database Shared memory, and their memory segments must be contiguous.
注意这个数量同时还包括实例共享内存和数据库共享内存，并且它们的内存段必须是邻接的。
In addition to actual files, devices and Shared memory objects can be mapped.
除了实际的文件，设备与共享内存对象都能够被映射。
These Settings increase the amount of Shared memory to 32 MB.
这些设置把共享内存总量增加到了32 MB。
The working storage pages for shared memory regions are not released until the shared memory region is deleted.
对于共享内存区域，直到删除共享内存区域之后，才会释放其工作存储分页。
Before converting them to Shared memory LPARS, I did some Numbers.
在把它们转换为共享内存lpar之前，我做了一些研究。
The Shared memory is not destroyed even after all processes detach from it.
即使在所有进程都与之脱离之后，这个共享内存也不会被销毁。
This article explains instance Shared memory and database Shared memory.
本文将介绍实例共享内存和数据库共享内存。
The failover is transparent to the Shared memory partitions.
故障转移对于共享内存分区是透明的。
Following the instance Shared memory is the database Shared memory.
紧接着实例共享内存的是数据库共享内存。
If the Shared memory already exists, it simply attaches to it.
如果共享内存已经存在，它就只是依附到现有的共享内存。
The Shared memory is not deleted when the process exits.
当主进程退出时，并不删除共享内存。
DB2 also USES Shared memory for various other heaps.
DB 2还将共享内存用于各种其他的堆。
Shared memory: Read a primer on Shared memory and learn more about the various implementations available.
共享内存：阅读关于共享内存的基础教程，进一步了解各种实现。
Note that the database Shared memory calculations show that we are still within available 1gb Shared memory limit.
注意，对数据库共享内存的计算表明，我们仍然没有超出1gb可用共享内存的限制。
When running, the subsystem's shared memory contains the actual usable configuration information.
当运行时，子系统的共享内存包含了实际有用的配置信息。
"Into Shared memory, and the latter reads and displays the string."
写入内存，另一个进程读取并显示此字符串。
The instance Shared memory and database Shared memory combined is around 3.7gb.
实例共享内存和数据库共享内存合起来大约是3.7GB。
In Figure 2, process a requests a segment of Shared memory.
在图2中，进程A请求一个共享内存段。
应用推荐