From: Paul Jackson <pj@sgi.com>
To: Olivier Galibert <galibert@pobox.com>
Cc: jesper.juhl@gmail.com, arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Is that an acceptable interface change?
Date: Mon, 6 Mar 2006 09:00:05 -0800 [thread overview]
Message-ID: <20060306090005.e5575140.pj@sgi.com> (raw)
In-Reply-To: <20060306161512.GB23513@dspnet.fr.eu.org>
> Please excuse me if I'm a little dense here, but the kernel headers
> _define_ the userspace-kernel interface.
I don't think so. The kernel headers define the API's that the
various kernel facilities present to each other, within the kernel.
The userspace-kernel interface is not really a simple interface
of procedures and types definable by a traditional C header.
It uses a variety of techniques, such as special calling conventions,
special files, and what not ... almost everything possible except
the simple call by one procedure of another on a common stack.
In the general case, we can do no more than document, from the
kernel side, what is the interface, and expect libraries and such
on the user side to wrap this up in a form palatable to C (and
other diverse) language uses.
Such header files as are useful to a userspace C programmer are
usually provided by the userspace library, for it is that library
that the application is linking with, not the kernel.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-03-06 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 1:17 Is that an acceptable interface change? Olivier Galibert
2006-03-06 7:52 ` Arjan van de Ven
2006-03-06 15:50 ` Olivier Galibert
2006-03-06 15:55 ` Jesper Juhl
2006-03-06 16:15 ` Olivier Galibert
2006-03-06 16:20 ` Jesper Juhl
2006-03-06 16:25 ` Randy.Dunlap
2006-03-06 17:00 ` Paul Jackson [this message]
2006-03-06 17:23 ` Christopher Friesen
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=20060306090005.e5575140.pj@sgi.com \
--to=pj@sgi.com \
--cc=arjan@infradead.org \
--cc=galibert@pobox.com \
--cc=jesper.juhl@gmail.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