People are throwing money at the problem. We're now at a point that in
order to provide the interested people with something they can use, we
need some kind of way to protect their applications against calling an
unsuspecting new mmap syscall instead of the aio syscall specified in
the kernel they compiled against.
> Maybe, just maybe, most people simply do not care one iota about AIO.
>
> Linux caters to the general concerns not the nooks and cranies, that
> is why it is anything but doomed.
What I'm saying is that for more people to play with it, it needs to be
more widely available. The set of developers that read linux-kernel and
linux-aio aren't giving much feedback. I do not expect the code to go
into 2.5 at this point in time. All I need is a set of syscall numbers
that aren't going to change should this implementation stand up to the
test of time.
-ben
-- Fish. - 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/