A real application would use semaphores or other techniques to control reading and writing to the Shared segment.
真实的应用程序会使用信号量或其他技术控制对共享内存段的读写。
Annexation is called mapping, where the Shared segment of memory is assigned local addresses in each process 'own address space. Figure 1, Figure 2, Figure 3, and Figure 4 depict the process.
这个连接过程称为映射，它给共享内存段分配每个进程的地址空间中的本地地址。
This effectively frees up one segment for database Shared memory.
这将有效地为数据库共享内存一个段。
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的共享内存限制，并且每个数据库共享内存段可以安全地连续映射到一个象限。
However, a Shared memory segment cannot be "split" across quadrants and be guaranteed a contiguous address space.
但是，共享内存段不能跨象限“拆分”，而应该保证是一个连续的地址空间。
If ESTORE is enabled, then it will take another segment away from the database Shared memory.
如果启用了ESTORE，那么还要从数据库共享内存中拿出另一个段。
Though FCM communication becomes faster, it reduces the database Shared memory by one segment.
虽然FCM通信变得更快，但是它也令数据库共享内存减少了一个段。
Dynamic segment allocation allows the additional segments to be used by user heap or Shared memory.
动态段分配让用户堆或共享内存可以使用额外的段。
Communications segment: the Shared memory communications portion, also known as the message portion, is used as a communication mechanism by the client and server processes.
通信段：共享内存通信区，也被称为消息区，被作为客户机和服务器进程的一种通信机制。
When the FCM buffers are created in a separate memory segment, the communication between FCM daemons of different logical partitions on the same physical node occurs through Shared memory.
而当在单独的内存段中创建F CM缓冲区时，在同一物理节点上的不同逻辑分区的FCM守护进程间的通信将通过共享存储器进行。
Therefore, if you enable ESTORE, make sure it is at least 256mb or else it would not make sense, because a segment of 256mb from the database Shared memory is taken for just managing the ESTORE.
因此，如果启用ESTORE，则应确保它至少是256MB，否则就不起作用，因为要从数据库共享内存中拿出一个256 MB的段来仅用于管理这个ESTORE。
Note: DB2 will take away one segment from the database Shared memory for each of the following configurations, starting from segment b.
注意：对于下面的每种配置，DB 2将从数据库共享内存中拿出一个段，这个段始于段b。
This forces DB2 to use segment E for local connections, thus freeing one segment for database shared memory.
这样便迫使DB2将段E用于本地连接，从而为数据库共享内存空出一个段。
The code implements a parent and child process that communicates via a shared memory segment.
代码实现通过共享内存段通信的父进程和子进程。
Segments 4 to B -The database shared memory starts at segment 4 and the segments must be attached contiguously.
段4到段B-数据库共享内存始于段 4，这些段必须紧挨在一起。
Therefore, the largest shared memory segment, in quadrant 3, that DB2 is allowed to allocate is 1GB; and in quadrant 4 is 0.75GB.
因此，DB2允许分配的最大共享内存段在象限3 中的大小为1GB，在象限4 中的大小为 0.75GB。
In Figure 2, process a requests a segment of Shared memory.
在图2中，进程A请求一个共享内存段。
This parameter specifies the maximum size in bytes of a Shared memory segment which can be allocated on the system.
该参数按字节指定系统中可以分配的共享内存段的最大大小。
Finally, in Figure 4, processes a and B can read and write from the Shared memory segment freely.
最后，在图4中，进程a和B可以随意读写共享内存段。
The SHMMAX specifies the maximum size in bytes of a shared memory segment which can be allocated on the system.
SHMMAX 按字节指定系统上可以分配的最大共享内存段。
Depending on the type and size of the segment, DB2 can specify to create it in quadrant 4. The database Shared memory set is still limited to approximately 1gb.
根据段的类型和大小，DB 2可以指定在象限4中创建段。数据库共享内存集仍然有大约1gb的限制。
As its name implies, Shared memory makes a segment of memory accessible to more than one process.
顾名思义，共享内存让一段内存可供多个进程访问。
All we know is that the database Shared memory ends at 0xfe002000, because starting at that address is a segment for anonymous memory.
我们只知道，数据库共享内存在0xfe002000结束，因为从这个地址开始的是一个用于匿名内存的段。
Segment 3 (blue) is allocated to instance shared memory;
段3 （蓝色）被分配给实例共享内存。
Lotus Domino begins using the first two available segments for user heap memory (0x3 and 0x4). Lotus Domino begins using the last segment (0xf) for Shared memory.
LotusDomino最初将前两个可用的段(0x3和0x4)作为用户堆内存，将最后一个段(0xf)作为共享内存。
Another common problem with allocating database Shared memory on Solaris is due to the fact that all pages of a Shared memory segment are pinned in physical RAM.
Solaris中另一个与分配数据库共享内存有关的常见问题是由于这样的一个事实导致的，即共享内存段的所有页都是固定在物理ram中的。
This indicates that the process tried to access a Shared memory segment that was corrupted for some reason, and will crash without calling "fatal_error" or "panic."
这表明，进程试图访问因某种原因已破坏的共享内存段，并将不调用“fatal_error”或“panic”而崩溃。
If the database is partitioned, or intra-parallel enabled, or connection concentrator enabled, then one segment is used for Application Group Shared Memory.
如果数据库是分区的，或者启用了intra - parallel或连接集中器，那么数据库共享内存中有一个段被预留给应用程序组共享内存。
The shmmax specifies the maximum size in bytes of a Shared memory segment which can be allocated on the system.
shmmax按字节指定了系统中可以分配的最大共享内存段。
msync(): Used to synchronize a shared memory segment with the file system—a technique useful when mapping a file into memory.
msync()：用来让共享内存段与文件系统同步 —当把文件映射到内存时，这种技术有用。
应用推荐