No. POSIX aio does not have any concept of a completion queue. Completion
in POSIX aio comes via a thread callback, signal delivery or polling, all
of which are horrendously inefficient.
> If not, testing with in-kernel things is sufficient. But
> if it does then it becomes more reasonable to transiently define some
> syscall numbers (high up, in some defined as "testing and like shifting
> sands" range) so user space can test the interface.
Maybe. The unfortunate aspect to this is that you can't tell if a number
matches the name you expect it to be, and invariably people end up running
the wrong code on the wrong kernel. Or vendors start shipping patches to
enable these new syscalls....
> Thought: is there a meta-syscall in the kernel API for calling other
> syscalls? You could have such a beast taking negative numbers for
> experimental calls...
I'm working on something. Stay tuned.
-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/