Re: Syslets, Threadlets, generic AIO support, v6

[Ingo Molnar <mingo@elte.hu>]

* Albert Cahalan <acahalan@gmail.com> wrote:

> Ingo Molnar writes:
> 
> >looking over the list of our new generic APIs (see further below) i
> >think there are three important things that are needed for an API to
> >become widely used:
> >
> > 1) it should solve a real problem (ha ;-), it should be intuitive to
> >    humans and it should fit into existing things naturally.
> >
> > 2) it should be ubiquitous. (if it's about IO it should cover block IO,
> >    network IO, timers, signals and everything) Even if it might look
> >    silly in some of the cases, having complete, utter, no compromises,
> >    100% coverage for everything massively helps the uptake of an API,
> >    because it allows the user-space coder to pick just one paradigm
> >    that is closest to his application and stick to it and only to it.
> >
> > 3) it should be end-to-end supported by glibc.
> 
> 4) At least slightly portable.
> 
> Anything supported by any similar OS is already ahead, even if it 
> isn't the perfect API of our dreams. [...]

it might have been so a few years ago but it's changing slowly but 
surely - BSD is becoming more and more irrelevant. What matters mostly 
to app writers these days: "is it in most Linux distros" - and the key 
to that is upstream kernel support and glibc support. The days of BSD 
(and UNIX) are pretty much numbered. (I'm not against standardizing APIs 
in POSIX of course - the BSDs tend to follow the Linux APIs in that area 
with a few years lag.)

	Ingo
-
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/