[cap-talk] Another "core" principle - virtualizing memory

[David Hopwood]

Jonathan S. Shapiro wrote:
> Claim 1:  A robust kernel must operate from fixed resource, ignoring
> the fact that it may make startup-time decisions about how to partition
> the available memory into individual resource types (what David Wagner
> and I have referred to elsewhere as type-specific heaps, and David
> Hopwood has described as preallocated vectors of object).

Nitpick: memory pools in general need not be used only for a single
type, and may not be implemented as an array/vector. Their advantages
come from separating allocations that should be independent of each other,
regardless of type or how the pool is implemented. It can also be a
simplification to have different threads allocating from different pools.

Of course, the simplest implementation, and the one that seems to be most
commonly used when memory pools are reimplemented for a specific application,
is to use arrays/vectors each of a single type.

-- 
David Hopwood <david.nospam.hopwood at blueyonder.co.uk>