Re: [boost] [pool] Definition of a static_pool ?

Subject: Re: [boost] [pool] Definition of a static_pool ?
From: Christopher Kormanyos (e_float_at_[hidden])
Date: 2012-04-28 06:44:03

>> Same here, I use both runtime defined size pools and compile-time defined size pools.

>> Joel Lamotte

> Having both classes sounds good, perhaps I will start by trying to add the runtime pool
> correctly (with test cases and documentation...) and afterward perhaps if
> Christopher and/or Joël could send me their implementation of compile-time pools,
> I could also include it in my development.
> Regards, Étienne

I was wrong. It looks like boost's development and my own development
simply overlap. It appears as though I merely reinvented the wheel on this one.
I often make this kind of mistake---charge ahead with my own
development before actually knowing what's there in the first place.

My methods simply parallel those of boost's fast_pool_allocator
(with a dummy Mutex template parameter) in combination with
boost's singleton_pool. So my code is very similar to boost's.

Sorry about that.

One other idea that may be of interest, though, is the concept
of "placing" a custom allocator and its associated pool at
a known physical address and granting these the one-shot allocation
character that you describe. I have used this technique in combination with
various sets of microcontroller registers to overly STL containers like a vector
on top of, say, the background readings from a hardware DMA.
In this way the DMA "fills up" your vector in a CPU-independent
fashion and the user can read the results from the underlying hardware
layer---properly packed in the container---with essentially zero cost.
I have not yet seen anyone else do this with the STL.

Best regards, Chris.