Data format and address space.
数据格式和地址空间。
Available virtual address space.
可用虚拟地址空间。
There is no need to switch address space.
这种切换不需要切换地址空间。
That’s it for virtual address space layout.
该图呈现了虚拟地址空间的管理方式。
Mapping it into the program's address space
将程序库映射到程序的地址空间。
Each MFC can access a separate address space.
每个MFC都可以访问一个单独的地址空间。
Import a logical address space from another module.
从其他模块中导入逻辑地址空间。
Hlq.CICS controls access from a CICS address space.
控制来自CICS地址空间的访问。
All it knows about is its own virtual address space.
它只知道自己的虚拟地址空间。
Increase the amount of address space available to you.
增加可用的地址空间量。
Now the data is stored in the user address space buffer.
现在数据被储存在用户地址空间缓冲区。
Each DB2 agent process has its own memory address space.
每个DB 2代理进程都有其自己的内存地址空间。
A module is an encapsulated private logical address space.
模块就是一个封装的、私有的逻辑地址空间。
In the logical address space we have new degrees of freedom.
在逻辑地址空间我们拥有了更大的自由。
All URI addresses are managed within a logical address space.
所有uri地址在一个逻辑地址空间中统一管理。
The address space is not entirely devoted to a single process.
地址空间并不完全用于单个的进程。
DB2 needs a contiguous address space for the Shared memory area.
DB 2需要一个连续的地址空间来作为共享内存区域。
It just inherits service class from its originator address space.
它简单地从原始地址空间继承服务分类。
Well then, how do we know how big a DB2 agent's address space is?
那么，我们怎么知道一个DB2代理的地址空间是多大呢？
The dynamic cache is also part of the application's address space.
动态缓存也是应用程序地址空间的一部分。
Free: the process is not yet using that area of the address space.
自由：还没有进程使用这部分地址空间。
Figure 6 shows the 32-bit memory address space for a DB2 agent process.
图6展示了用于一个DB 2代理进程的32位内存地址空间。
Systems utilizing 64 bits for the address space have virtually no limits.
而使用 64位地址空间的系统实际上是没有这种限制的。
However, running programs in a virtual address space has an associated cost.
然而，在虚拟地址空间中运行程序也会带来相应的成本。
Observe that OEMPUTX reports the CPU cost by individual broker address space.
观察OEMPUTX按照单个代理地址空间报告cpu成本。
This means, all the VMs live in the same OS address space and run in parallel.
这表示所有的虚拟机都驻留在同一个操作系统的地址空间中并且并行运行。
So far, you've located the heap within the address space, based only on its size.
到目前为止，我们只是在根据大小来了解堆在地址空间中的分配情况。
So far, you've located the heap within the address space, based only on its size.
到目前为止，我们只是在根据大小来了解堆在地址空间中的分配情况。
应用推荐