紧接着实例共享内存的是数据库共享内存。
Following the instance Shared memory is the database Shared memory.
共享内存的大小确定一次能够使用多少个实例。
The size of the Shared memory determines how many instances can be used at once.
truncate方法以字节为单位设置共享内存的大小。
The truncate method sets the size of the shared memory in bytes.
限制：在此配置中，对于数据库共享内存的限制是2gb或8个段。
Limit: In this configuration, the limit for database Shared memory is 2gb, or 8 segments.
除了上述参数以外，还有一个参数也会影响数据库共享内存的数量。
In addition to the above parameters, there is another parameter which also affects the amount of database Shared memory.
如果您选择的值未被接受，那么必须修改内核的最大共享内存的大小。
You may also have to tweak your kernel's maximum shared memory size if the value you choose isn't accepted.
在默认情况下，数据库共享内存的大小是1.75GB减去堆栈大小。
By default, the database Shared memory is 1.75gb minus the Stack.
instance_memory参数只是设置了实例共享内存的限制。
The instance_memory parameter only sets the limit for the instance Shared memory.
共享内存：阅读关于共享内存的基础教程，进一步了解各种实现。
Shared memory: Read a primer on Shared memory and learn more about the various implementations available.
计算性分页是一些用于文本、数据、堆栈和进程的共享内存的分页。
Computational pages are pages used for the text, data, stack, and Shared memory of a process.
我们的目标程序使用自旋锁机制来实现线程间对共享内存的互斥访问。
The classic spin lock technology is introduced to implement the mutually exclusive access to Shared memory.
基于同样的原因，这类API也非常适合多个进程并发执行和共享内存的服务器。
For the same reason, they are also particularly efficient on servers where many processes run concurrently and memory is Shared.
在默认情况下，实例共享内存的起始地址固定于0x10000000。
By default, the starting address of the instance Shared memory is fixed at 0x10000000.
对于希望访问已经创建的共享内存的进程，第一个参数应该是open_only。
For a process that wants to have access to an already-created Shared memory, the first argument should be open_only.
使用Linux2.6.16内核时，必须根据共享内存的分配方式进行一些更改。
With the Linux 2.6.16 kernel, some changes have been made in the way this shared memory is allocated.
因为实例共享内存的结束地址不固定，所以数据库共享内存的起始地址也是不固定的。
Since the end address of the instance Shared memory is not fixed, the starting address for the database Shared memory is not fixed either.
注意，对数据库共享内存的计算表明，我们仍然没有超出1gb可用共享内存的限制。
Note that the database Shared memory calculations show that we are still within available 1gb Shared memory limit.
但真的没有办法让用户空间和内核之间共享内存的安全时，他们只是作为一个缓冲？
But is there really no way of making memory Shared security between user space and kernel when they are just used as a buffer?
由于这些内存段的大小不是固定的，我们只能估计实例共享内存和数据库共享内存的大小为。
Since the sizes of all these memory segments are not fixed, we can only estimate the size of the instance and database Shared memory to be.
共享内存的实现有点儿复杂，尽管如此，对于多个进程之间的主机内协作，共享内存是不错的方法。
Shared memory is slightly more complicated to implement but is otherwise an excellent choice for intra host collaboration between multiple processes.
每个连接到数据库的应用程序都会被分配内存；因此，正确地配置会影响应用程序共享内存的参数非常重要。
Each application connected to the database has memory allocated to it; therefore accurate configuration of the parameters affecting the application Shared memory becomes crucial.
这类问题主要是因为许多用户越来越多地争用资源引起的（比如，随着用户数量的增加，共享内存的使用在增加）。
This type of issue is mainly caused by the growing resource contention with the number of users (for example, shared memory usage grows as the number of users increase).
Initializer定义了共享内存的id m_shmid和一个用来处理同步事件的信号量ms _ mutex。
Initializer defines Shared memory id m_shmid and a semaphore ms_mutex for synchronous event handling.
共享内存的位置存储在句柄中，从OPEN_LOG到后续的LOGGER和LOGINFO调用都会传递这个句柄。
This Shared memory location is stored in the handle passed from the OPEN_LOG procedure to the subsequent calls to LOGGER and LOGINFO.
PagingVIOS设备为共享内存池提供分页服务，为共享内存的LPAR管理Hypervisor分页空间。
This paging VIOS device provides paging services for the Shared memory pool and manages the Hypervisor paging Spaces for Shared memory LPARs.
其中一个包含标记名的共享内存的位置及其日志操作，第二个结构包含调用DB 2 . OPEN_LOG时的时间戳。
One of them contains Shared memory location of the token and its logging actions, and the second structure contains the timestamp of when the DB2.OPEN_LOG was invoked.
在Linux/390 上，用于共享内存的区域从0x50000000 开始，并且必须在 0x7fffa000 之前结束。
On the Linux/390, the area for shared memory starts at 0x50000000 and must end before 0x7fffa000.
在当前使用的AIX大内存模型中，ConstrainedSHMSizeMB应该只用来支持需要共享内存的第三方应用程序。
In the currently used AIX large memory model, ConstrainedSHMSizeMB should be used only to support third-party applications that require Shared memory.
数据库服务器分配给排序的虚拟共享内存的数量取决于要进行排序的行数、每一行的大小以及是否为服务器设置了PDQPIORIDY。
The amount of virtual Shared memory that the database server allocates for a sort depends on the number of rows to be sorted and the size of the row, and whether PDQPIORIDY is set for the server.
数据库服务器分配给排序的虚拟共享内存的数量取决于要进行排序的行数、每一行的大小以及是否为服务器设置了PDQPIORIDY。
The amount of virtual Shared memory that the database server allocates for a sort depends on the number of rows to be sorted and the size of the row, and whether PDQPIORIDY is set for the server.
应用推荐