Hello,
SlabPoolImpl , all public methods share the same lock.
All memory allocation are performed inside the synchronized context...
I would be happy to fix the implementation , but would like to get answers
to these question first:
If there is a need of truly exact size limits ? ,if so all set size changing
operations will be forced to be synchronized, no need for concurrenthashmap.
Is there a real need to have the functionality to close ?, should that not
be handled in a more natural indirect way ?
--
regards
gustav trede