![]() | ||||||||||
Messages in this thread |
>Since the guts of NT are basically VMS warmed over (hmmm, that would make >it RSX11M mk III), "asynchronous I/O" probably means the ability to >request that the kernel start an I/O and send a signal when it is >complete. Meanwhile the user process goes on doing other stuff. >Traditionally Unix-like systems do this by forking. Linux can do better >than that, with threads. (VMS I/O forking is a special case of >multithreading.) So probably the only thing that is missing is some >syntactic sugar to package the I/O thread(s) conveniently. >Did I get it right? See http://www.microsoft.com/win32dev/base/scalabil.htm for a Microsoft article on writing scalable Win32 apps. Click the search button at the top of the screen and type in "I/O Completion Ports" and/or "overlapped I/O" for related information. Back to Linux. . . -mike | |||||||||
| Last update: 2005-03-22 12:38 [from the cache] ©2003-2008 | ||||||||||