From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
Linus Torvalds <torvalds@osdl.org>,
David Woodhouse <dwmw2@infradead.org>,
David Howells <dhowells@redhat.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
libc-alpha@sources.redhat.com
Subject: Re: Proposal for a userspace "architecture portability" library
Date: Sat, 04 Dec 2004 21:06:30 -0700 [thread overview]
Message-ID: <41B28946.5010904@starnetworks.us> (raw)
In-Reply-To: <1102214647.5520.133.camel@gaston>
Benjamin Herrenschmidt wrote:
> Interesting ... note also that it goes well with my intend of having
> some of these (atomics, locks, ...) be provided by the kernel via the
> vDSO library mapped by the kernel in userland on ppc. That library would
> abstract that nicely. (That way, the kernel can take care of providing
> the best implementation for a given processor, dealing with CPU errata
> that often happen around areas of locks & atomics, etc...)
Another thought... the Apache APR library already attempts to provide
some of this functionality (atomic operations and locks, among others).
This would fit nicely, as it would provide the underlying core for these
operations, and allow APR to be extremely well optimized when built for
a Linux platform.
next prev parent reply other threads:[~2004-12-05 4:13 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
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 [this message]
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=41B28946.5010904@starnetworks.us \
--to=kpfleming@starnetworks.us \
--cc=benh@kernel.crashing.org \
--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=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