On Wed, Aug 09, 2006 at 01:31:24PM -0700, Matt Stupple wrote:
> I'm trying to find out the semantics of
> umem_cache_alloc/umem_cache_free. In general I expect that buffers
> allocated from a umem_cache and then returned to the cache with
> umem_cache_free *remain* in the cache and will possibly be
>[Some explanation: for use in a lock-free queue implementation I need a object
>'pool' where freed
objects remain available in the pool (as they may still be accessed by other
threads after one thre
ad has freed them) and I was hoping to build this facility using a
umem_cache...]
You don't g
I'm trying to find out the semantics of umem_cache_alloc/umem_cache_free. In
general I expect that buffers allocated from a umem_cache and then returned to
the cache with umem_cache_free *remain* in the cache and will possibly be
returned from subsequent calls to umem_cache_alloc; but under what
