Asynchronous I/O
Nov. 16th, 2000 11:34 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
pphaneufLinus Torvalds is a freakin' genius. I find some problem with his proposed API because of the fact that the events are edge-triggered, and I like being able to read or write only a limited amount and have the event trigger again to continue (so that all connections are given a fair chance).
Actually, that's what I thought upon first reading this, but you see, the guy is really a freakin' genius!
It's not a perfect proposal (means many system calls for binding file descriptors, if you want to rebind after every event), but it's a really good idea. The bind_event system call could be made user-space and its functionality rolled into the get_events system call, so that the next time get_events is called, it gets the events to bind/rebind, and then returns what's new.
I know there are racy problems with this last paragraph, but they could be fixed, I just don't know how (did I mention Linus is a freakin' genius?)...
Actually, that's what I thought upon first reading this, but you see, the guy is really a freakin' genius!
It's not a perfect proposal (means many system calls for binding file descriptors, if you want to rebind after every event), but it's a really good idea. The bind_event system call could be made user-space and its functionality rolled into the get_events system call, so that the next time get_events is called, it gets the events to bind/rebind, and then returns what's new.
I know there are racy problems with this last paragraph, but they could be fixed, I just don't know how (did I mention Linus is a freakin' genius?)...
