public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.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: Sun, 5 Dec 2004 15:29:09 -0800	[thread overview]
Message-ID: <20041205232909.GE26040@ca-server1.us.oracle.com> (raw)
In-Reply-To: <16818.23575.549824.733470@cargo.ozlabs.ibm.com>

On Sun, Dec 05, 2004 at 11:53:43AM +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'd love to see this also.  We've wrapped kernel-style bitops
from ext2 in
http://oss.oracle.com/projects/ocfs2-tools/src/trunk/libocfs2/include/bitops.h
(code is very similar to the libext2fs version).  We've also done the
kernel endian macros in userspace (glibc) in
http://oss.oracle.com/projects/ocfs2-tools/src/trunk/libocfs2/include/byteorder.h.
These might be useful (or not).  Also, I'd suggest list.h and
rbtree.[ch].  We use them extensively, as they are nice implementations
with little to no dependancies on anything else.
	Again, we've taken the approach of not including kernel headers,
instead making the kernel interface work via userspace methods.  I would
love to leave that work up to this library, and then just use it.

Joel

-- 

	Pitchers and catchers report.

Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2004-12-05 23:29 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
2004-12-05 18:12 ` Alan Cox
2004-12-05 19:48 ` Joseph Seigh
2004-12-05 23:29 ` Joel Becker [this message]
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=20041205232909.GE26040@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox