On Thu, 25 Jul 2002 16:28, H. Peter Anvin wrote:
> It seems to me that a reasonable solution for how to do this is not
> for user space to use kernel headers, but for user space and the
> kernel to share a set of common ABI description files[1]. These files
> should be highly stylized, and only describe things visible to user
> space. Furthermore, if they introduce types, they should use the
> already-established __kernel_ namespace, and of course __s* and __u*
> could be used for specific types.
I like it (having just argued for it), except for the __s* and __u*.
The ABI definitions aren't for kernel programmers. They are for
userspace programmers. So we should use standard types,
even if they are a bit ugly (and uint16_t isn't really much uglier
than __u16, and at least it doesn't carry connotations of
something that is meant to be internal, which is what the standard
double-underscore convention means).
Please, let us agree that the ABI definition should use standard
types wherever possible.
Brad
-- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 30 2002 - 14:00:19 EST