Memory Management

[Frank V. Castellucci]

CoreLinux++ should provide abstracts and default
implementations for:

1. Memory pools
2. Unnamed memory pool
3. Shared unnamed memory pool
4. Named memory pool management
5. Shared named-memory pool management

[Frank V. Castellucci]

Memory Management should handle sparse allocation and protection.

[Frank V. Castellucci]

Memory management should be able to take a mapping declaration that defines the type layout in the memory space.

[Frank V. Castellucci]

Linux shared memory maps the same shared memory into different virtual address across process boundries.

In this eventuality (disjoint processes), any type of structure (blob, matrix, class, etc.) that is to reside in a shared memory allocation needs to desribe itself using offsets.

[Frank V. Castellucci]

The mapping of structures in a shared memory arena should be available for reasoning from any process requiring access.

[Frank V. Castellucci]

The CoreLinux++ libraries shall have a unique named shared memory arena which manages the registration and access of instance shared memory structure mappings.

[Frank V. Castellucci]

The CoreLinux++ library shall provide a proxy class which can be used in the user applications for accessing and modifying the content of a structure in a named shared memory that has a registered mapping in the CoreLinux++ unique ontology segment.

[Frank V. Castellucci]

Memory Management should provide a way to specify a guard page and a handler for when the guard page faults.