The inventive method and data can prevent memory read damage with segment memory function or region memory function.
本发明提供的方法及装置防止具有分块存储功能或分区存储功能的存储器读损。
This effectively frees up one segment for database Shared memory.
这将有效地为数据库共享内存一个段。
However, a Shared memory segment cannot be "split" across quadrants and be guaranteed a contiguous address space.
但是，共享内存段不能跨象限“拆分”，而应该保证是一个连续的地址空间。
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的共享内存限制，并且每个数据库共享内存段可以安全地连续映射到一个象限。
Segment 2 is for stack and dynamic memory allocation.
段2预留给堆栈和动态内存分配。
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。
If ESTORE is enabled, then it will take another segment away from the database Shared memory.
如果启用了ESTORE，那么还要从数据库共享内存中拿出另一个段。
Segment 3 - Reserved for instance Shared memory.
段3-预留给实例共享内存。
Though FCM communication becomes faster, it reduces the database Shared memory by one segment.
虽然FCM通信变得更快，但是它也令数据库共享内存减少了一个段。
This forces DB2 to use segment E for local connections, thus freeing one segment for database shared memory.
这样便迫使DB2将段E用于本地连接，从而为数据库共享内存空出一个段。
Segment 2 - Reserved for agent private memory.
段2-预留给代理私有内存。
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.
通信段：共享内存通信区，也被称为消息区，被作为客户机和服务器进程的一种通信机制。
Even though the data segment maps a file, it is a private memory mapping, which means that updates to memory are not reflected in the underlying file.
尽管数据段映射了文件，但这种内存映射是私有的，也就是说，数据段的内存更新不会在其映射的文件中生效。
Take a book and imagine each page in the book representing a memory segment.
来看一下，并假设书中的每页表示一个内存段。
The code implements a parent and child process that communicates via a shared memory segment.
代码实现通过共享内存段通信的父进程和子进程。
The text segment also maps your binary file in memory, but writes to this area earn your program a Segmentation Fault.
文本段同样会将二进制文件映射到内存，但文件映射区域的写入操作只能以程序收到段错误而告终。
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守护进程间的通信将通过共享存储器进行。
Virtual memory segment: This virtual portion is used for maintaining and controlling the resources needed by processes.
虚拟内存段：虚拟区用于维护和控制进程所需的资源。
Segments 4 to B -The database shared memory starts at segment 4 and the segments must be attached contiguously.
段4到段B-数据库共享内存始于段 4，这些段必须紧挨在一起。
TLB is used to try and retrieve translation work that has already occurred, and this is the first place the operating system will look for a process's translated memory segment.
TLB用于尝试和检索已经发生的转换工作，而这是操作系统第一次查找进程的已转换内存段的地方。
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。
The end address of the instance Shared memory segment is not fixed.
实例共享内存的结束地址是不固定的。
Process a initializes the memory segment, preparing it for use.
进程A对这个内存段进行初始化，让它准备好接受访问。
The SHMMAX specifies the maximum size in bytes of a shared memory segment which can be allocated on the system.
SHMMAX 按字节指定系统上可以分配的最大共享内存段。
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可以随意读写共享内存段。
Segment 3 (blue) is allocated to instance shared memory;
段3 （蓝色）被分配给实例共享内存。
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或连接集中器，那么数据库共享内存中有一个段被预留给应用程序组共享内存。
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”而崩溃。
应用推荐