Open tiran opened 8 years ago
How about using the wiki instead?
Gilectomy has already gilhub issue for this (closed) and even an open bounty!
On Monday, June 6, 2016, larryhastings notifications@github.com wrote:
How about using the wiki instead?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/larryhastings/gilectomy/issues/29#issuecomment-224166719, or mute the thread https://github.com/notifications/unsubscribe/AHgZ5Z4hn9vHv2Ilo8NH5qk5ArxIR1nlks5qJOu3gaJpZM4Ivh0t .
Hi.
I am the author of liblfds.
If I can assist in any way, please let me know. I've commented also in the original github issue, https://github.com/larryhastings/gilectomy/issues/18
gilectomy doesn't have a mailing list to discuss ideas yet. I'm using the tracker to keep a record of my idea.
I had a conversation with William Brown, a co-worker and developer of the 389 Directory Server. He has been working on lock free database for 389 DS [1]. William pointed me to liblfds [2], an open source library with lock-free data structures. liblfds provides freelist and queues. The wiki also contains good information on memory barriers and CAS.
[1] http://firstyear.id.au/blog/html/2016/06/07/lock_free_database.html [2] http://liblfds.org/