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

[Jonathan S. Shapiro]

On Wed, 2007-01-03 at 23:01 +0000, David Hopwood wrote:
> 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.

Yes. In fact, early versions of BSD kmalloc were often partitioned by
the size of the allocated unit rather than the type. The introduction of
named pools (all elements of a pool required to be of same size) came
later.
-- 
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100