Scribd
Upload
37 views

Linux Io Apis Mark Veltzer

Linux IO APIs have problems where calling read() puts the process to sleep until the read ends, which takes a long time since it involves reading from disk. This sleep time could be faster if reading from network or RAM file system instead of disk. Asynchronous IO APIs were created to address this by allowing other processes to run while waiting for IO to complete without blocking the calling process.

Uploaded by

Mark Veltzer
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODP, PDF, TXT or read online on Scribd
37 views

Linux Io Apis Mark Veltzer

Linux IO APIs have problems where calling read() puts the process to sleep until the read ends, which takes a long time since it involves reading from disk. This sleep time could be faster if reading from network or RAM file system instead of disk. Asynchronous IO APIs were created to address this by allowing other processes to run while waiting for IO to complete without blocking the calling process.

Uploaded by

Mark Veltzer
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODP, PDF, TXT or read online on Scribd
You are on page 1/ 2

Linux IO APIs Mark Veltzer mark@veltzer.

net

The problems with IO APIs

When you call read(2) your process is put to sleep until the read ends. This sleep lasts quite some time since you are not supposed to wake up until the buffer is full and reading from disk takes quite some time. If the device you are reading from is not disk, but rather network or RAM file system then the sleep time could be much faster.

You might also like