lotus

previous page: 5.1. (DCE, POSIX, UI) Async safety (Programming threads)
  
page up: Threads Programming FAQ
  
next page: 5.3. Context switch (Programming threads)

5.2. Asynchronous and blocking system calls (Programming)




Description

This article is from the Threads Programming FAQ, by Bryan O'Sullivan bos@serpentine.com with numerous contributions by others.

5.2. Asynchronous and blocking system calls (Programming)

Most system calls, whether on Unix or other platforms, block (or
"suspend") the calling thread until they complete, and continue its
execution immediately following the call. Some systems also provide
asynchronous (or "non-blocking") forms of these calls; the kernel
notifies the caller through some kind of out-of-band method when such
a system call has completed.

Asynchronous system calls are generally much harder for the programmer
to deal with than blocking calls.

 

Continue to:













TOP
previous page: 5.1. (DCE, POSIX, UI) Async safety (Programming threads)
  
page up: Threads Programming FAQ
  
next page: 5.3. Context switch (Programming threads)