Implementation Details

Note: IBM reserves the right to change these implementation details in future releases of OS/2.

Any number specified in VIRTUALADDRESSLIMIT is rounded up to a 64 MB boundary.

The user's address space above the 512 MB line has the same properties as the user's address space below the 512 MB line, namely:

• A high private arena at the low end and a high shared arena at the high end.

• of the user's address space is guaranteed to be in the high private arena

• of the user's address s[ace is guaranteed to be in the high shared arena

• The two arenas grow toward each other: the high private arena grows up and the high shared arena grows down.

No memory objects can span the 512 MB line.

The current allocation strategy for OBJ_ANY allocations is: Allocate from the appropriate high memory arena. If there is not enough virtual memory in the specified arena to support the request, then the allocation will come from the appropriate low memory arena below the 512 MB line, if possible. Otherwise, the function will fail with a return code of ERROR_NOT_ENOUGH_MEMORY.

---

[Back: New OBJ_ANY Memory Attribute]
[Next: High Memory Support Functions]