From: admin <admin@liblfds.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: lock-free data structure library ported to Linux kernel
Date: Tue, 31 May 2016 12:07:13 +0300 [thread overview]
Message-ID: <574D5441.6060709@liblfds.org> (raw)
Hi, everyone.
This is my first post to the linux-kernel list.
I am the author of a lock-free data structure library, liblfds, which
has now my first attempt at a port to the Linux kernel, which is to say,
I have a Kbuild file which produces a static library.
I'm posting as I thought it might be of some interest. Please forgive
me if not!
The library performs no memory allocation, has no OS or standard library
dependencies, compiles on a bare C89 compiler, where the Linux kernel
port is dependent on GCC 4.1.2 or greater, and so supports every
processor GCC provides atomic intrinsics for. Documentation is
exhaustive (a wiki page per function, enum, struct, etc, etc).
The benchmark programme compares liblfds against locking mechanisms for
the same benchmarks, and produce eyecand^Hgnuplots.
http://liblfds.org/pages/images/liblfds710_btree_au_readn_then_writen_numa_Core%20i5%20%28x64%29.1200x1800.png
The set of data structures is quite limited. There's a couple of little
add-only data structures (btree, list, hash) and the a freelist/stack,
couple of queues and a ringbuffer. It is however surprising how often
add-only data structures are still perfectly viable. There's a
lock-free, delete supporting red-black tree in the literature, which
looms large now in my mind.
The library can be found here;
http://www.liblfds.org
Release 7.1.0 was published about thirty minutes ago :-)
next reply other threads:[~2016-05-31 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:07 admin [this message]
2016-05-31 18:13 ` lock-free data structure library ported to Linux kernel Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=574D5441.6060709@liblfds.org \
--to=admin@liblfds.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox