From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: Paul Mackerras <paulus@samba.org>
Cc: Robert Love <rml@novell.com>, Linus Torvalds <torvalds@osdl.org>,
David Woodhouse <dwmw2@infradead.org>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com
Subject: Re: Proposal for a userspace "architecture portability" library
Date: Sat, 04 Dec 2004 19:10:03 -0700 [thread overview]
Message-ID: <41B26DFB.6060003@starnetworks.us> (raw)
In-Reply-To: <16818.26777.209451.685576@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> No, for semaphores and rwsems I was going to use futexes. Or maybe we
> don't need the kernel's semaphores, rwsems and spinlocks in userspace
> at all. I'm open to suggestions.
I think that _all_ of these items can find use in userspace, if they are
usable with glibc's threading implementation and the other userspace
issues that would be involved.
I for one would love to be able to use lightweight rwsems and spinlocks
in an application I'm working on, but it's entirely userspace and it
would be impossible for _me_ to pick out this code from the kernel tree
and make it work on any architecture that I don't have here (which is
all of them except x86 <G>).
next prev parent reply other threads:[~2004-12-05 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 0:53 Proposal for a userspace "architecture portability" library Paul Mackerras
2004-12-05 1:08 ` Robert Love
2004-12-05 1:47 ` Paul Mackerras
2004-12-05 2:10 ` Kevin P. Fleming [this message]
2004-12-05 3:51 ` Roland McGrath
2004-12-05 2:40 ` H. Peter Anvin
2004-12-05 2:44 ` Benjamin Herrenschmidt
2004-12-05 4:06 ` Kevin P. Fleming
2004-12-05 18:12 ` Alan Cox
2004-12-05 19:48 ` Joseph Seigh
2004-12-05 23:29 ` Joel Becker
2004-12-06 9:42 ` Adrian 'Dagurashibanipal' von Bidder
-- strict thread matches above, loose matches on Subject: below --
2004-12-05 6:18 Dan Kegel
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=41B26DFB.6060003@starnetworks.us \
--to=kpfleming@starnetworks.us \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rml@novell.com \
--cc=torvalds@osdl.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