Zach Brown just posted to lkml (a few minutes ago) ...
[PATCH 0 of 4] Generic AIO by scheduling stacks It's a syscall to submit syscalls to run async. Then another syscall to async gather the results of the submitted syscalls as they complete. One of the most wonderful things I've seen in awhile! Any syscall!
And I'm especially happy that
(
Read more... )
Comments 6
Reply
Reply
Reply
"Fibrils"? Didn't the Windows folks call these "fibers"?
As Linus said--the design is obvious, but the odds of a correct implementation are low. Threads are hard to get right. Userland AIO via kernel threads is great in principle, but I'll be surprised to see it done right in practice.
Still, I'd rather a relatively clued kernel hacker try to write the code than your J. Average Codemonkey try to do it in userspace with pthreads.
Reply
Reply
It makes me want to start on httpd 3.0... async everything. mmmmm.
Reply
Leave a comment