Need way to shrink the freelist about lockfree

[timblechmann]

not really:

• freeing memory is not lock-free
• freeing memory needs some safe memory reclamation algorithm like pass the buck or hazard pointers. both are patented.

one could add a method to have an 'unsafe' memory reclamation, which has undefined behavior when multiple threads access the queue, but i'm not a big fan of adding unsafe API as people won't be aware of the consequences.

[stephenmax-zhang]

Thank you for your reply.
The "request burst" I talking about is not too often, but due to the mass amount lockfree.queue instances I used, I must take care of this.
I have appropriate timing window to shrink the queue (i.e. when I certain it will not accessed by other thread), and it only need to be shrinked after every long period per session, so "freeing memory is not lock-free" is not my problem.
Adding the shrinking API is too difficult for me, so I appreciate if it comes from the author.
Sorry for my poor english~