LWN.net Logo

Asynchronous buffered file I/O

Asynchronous buffered file I/O

Posted Jan 9, 2007 16:53 UTC (Tue) by nix (subscriber, #2304)
In reply to: Asynchronous buffered file I/O by ldo
Parent article: Asynchronous buffered file I/O

The problem is that the vast majority of all I/O ops are synchronous, so needing multiple syscalls for them is unnecessary overhead. (You might think `who cares, the I/O will dominate', but it may not with e.g. fast network cards).

Plus, synchronous I/O was there first (I suspect this is the *real* reason why it gets syscalls of its own).


(Log in to post comments)

Asynchronous buffered file I/O

Posted Jan 10, 2007 5:57 UTC (Wed) by ldo (subscriber, #40946) [Link]

The extra overhead didn't matter for low-performance applications.

The high-performance applications tended to be written to use ASTs to report I/O completion.

Copyright © 2012, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds