> 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 <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
