From: Joe Seigh <jseigh_02@xemaps.com>
To: linux-kernel@vger.kernel.org
Subject: Possible killer app for user space RCU+SMR
Date: Tue, 18 Oct 2005 16:55:13 -0400 [thread overview]
Message-ID: <dj3n8k$7av$1@sea.gmane.org> (raw)
I've been trying to come up with a good application for user space RCU+SMR.
This has been problematic since most apps these days are pretty bloated and
overloaded with features, so you're talking about a huge amount of effort which
is why I haven't done a lock-free database at this point but have been looking
for something a little more doable.
What about nscd, the name service cache daemon? It's possible to rewrite the
cache data structures to be reader lock-free, put them into a shared memory
segment, and be able to resolve lookups from cache without any syscall or ipc
overhead. If the lookup wasn't satisfied from cache then you would use a
syscall to communicate with nscd. Is this worthwhile? As it is, does the current
implementation of nscd provide actual performance benefits or is it just around for
the coolness factor?
Note this technique could be extended to allow direct reading of kernel data
structures mapped into shared memory segments as well if anyone found a
use for that.
--
Joe Seigh
reply other threads:[~2005-10-18 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='dj3n8k$7av$1@sea.gmane.org' \
--to=jseigh_02@xemaps.com \
--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
Powered by JetHome