From: Robert Love <rml@novell.com>
To: Paul Mackerras <paulus@samba.org>
Cc: 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 20:08:44 -0500 [thread overview]
Message-ID: <1102208924.6052.94.camel@localhost> (raw)
In-Reply-To: <16818.23575.549824.733470@cargo.ozlabs.ibm.com>
On Sun, 2004-12-05 at 11:53 +1100, Paul Mackerras wrote:
> Some of our kernel headers implement generally useful abstractions
> across all of the architectures we support. I would like to make an
> "architecture portability" library, based on the kernel headers but as
> a separate project from the kernel, and intended for use in userspace.
I think that this is an _awesome_ idea. Might want to check out what
overlap there is with existing glibc interfaces. For example, I presume
that glibc implements at least some of the atomic operations (but I also
think having a full suite of atomic operations available is useful).
Some of the stuff, like semaphores, isn't really going to port very well
to user-space. At least not directly, I would not think.
But on numerous occasions I have wanted the kernel's barriers, atomic
operations, bitwise operations, or some of the compiler things we
implement (likely, unlikely, fixes) in user-space.
> Now, clearly I can do this under the GPL. However, I think it would
> be more useful to have the library under the LGPL, which requires
> either getting the permission of the authors of the kernel files, or
> rewriting them from scratch.
FWIW, you have my permission. I've touched spinlock.h a bunch.
Robert Love
next prev parent reply other threads:[~2004-12-05 1:07 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 [this message]
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
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=1102208924.6052.94.camel@localhost \
--to=rml@novell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.