But is there really no way of making memory Shared security between user space and kernel when they are just used as a buffer?
但真的没有办法让用户空间和内核之间共享内存的安全时，他们只是作为一个缓冲？
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.
它的构造函数创建共享内存及其中的对象。
This class stores the Shared memory identifier.
这个类存储共享内存标识符。
This effectively frees up one segment for database Shared memory.
这将有效地为数据库共享内存一个段。
Object a starts right at the beginning of Shared memory.
对象A直接从共享内存的起始处开始。
However, Shared memory segments still can not cross quadrant boundaries.
不过，共享内存段依然不能跨越象限边界。
These limits dictate how we configure each of the memory pools in the database shared memory set.
这些限制规定了我们该如何配置数据库共享内存集中的每个内存池。
The failover is transparent to the Shared memory partitions.
故障转移对于共享内存分区是透明的。
定义一个共享内存池。
DB2 also USES Shared memory for various other heaps.
DB 2还将共享内存用于各种其他的堆。
Table 5. Configuration parameters that affect application Shared memory.
表5.影响应用程序共享内存的配置参数。
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.
至此，我们已经讨论了实例共享内存、数据库共享内存和应用程序组共享内存以及代理私有内存。
Quadrant 4 (0.75gb) is reserved for Global Shared memory.
象限4 (0.75GB)被预留给全局共享内存。
Segment 3 - Reserved for instance Shared memory.
段3-预留给实例共享内存。
Since the end address of the instance Shared memory is not fixed, the starting address for the database Shared memory is not fixed either.
因为实例共享内存的结束地址不固定，所以数据库共享内存的起始地址也是不固定的。
A similar solution is using 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的共享内存限制，并且每个数据库共享内存段可以安全地连续映射到一个象限。
The memory areas are known as the Shared memory segments.
内存区域是已知的作为共享内存的段。
Note this amount includes both the instance Shared memory and database Shared memory, and their memory segments must be contiguous.
注意这个数量同时还包括实例共享内存和数据库共享内存，并且它们的内存段必须是邻接的。
The limit for database shared memory is around 3.5GB.
数据库共享内存的限制大约是 3.5GB。
The application group memory set is allocated from the database Shared memory set.
应用程序组内存集是从数据库共享内存集中分配的。
But what does Shared memory and private memory mean?
但是共享内存和私有内存的意义是什么呢？
The working storage pages for shared memory regions are not released until the shared memory region is deleted.
对于共享内存区域，直到删除共享内存区域之后，才会释放其工作存储分页。
Same logic applies to the instance Shared memory and the application group Shared memory.
这样的逻辑同样适用于实例共享内存和应用程序组共享内存。
This leaves more room for other memory sets such as the database Shared memory.
这样就将更多的空间留给了其他内存集，例如数据库共享内存。
This article explains instance Shared memory and database Shared memory.
本文将介绍实例共享内存和数据库共享内存。
Following the instance Shared memory is the database Shared memory.
紧接着实例共享内存的是数据库共享内存。
应用推荐