User: Password:
Subscribe / Log in / New account

regarding generic AIO, async syscalls precedent + some benchmarks by lighttpd

From:  bert hubert <>
To:  Zach Brown <>
Subject:  regarding generic AIO, async syscalls precedent + some benchmarks by lighttpd
Date:  Sun, 4 Feb 2007 23:55:41 +0100
Cc:  Benjamin LaHaise <>, Ingo Molnar <>,,, Suparna Bhattacharya <>, Linus Torvalds <>
Archive-link:  Article, Thread

From two comments posted to my "blog"

Excerpted from the diary of Dragonfly BSD, 

 Remove the asynchronous syscall interface. It was an idea before its time.
 However, keep the formalization of the syscall arguments structures.

The original async syscall interface was committed in

Comment by Jan Kneschke, lighttpd developer, noting the lack of and need for

 Reading this article feels like reading the code I wrote in the last days
 for lighttpd. Even if the network-io was async since the start
 (non-blocking), the file-io wasn't. Worst of all was the stat() syscall
 which doesn't have a async interface even in POSIX AIO. So it had to be
 implemented with threads on our own. At
 you can see the impact of async vs. blocking syscalls.

Perhaps relevant.

--      Open source, database driven DNS Software              Open and Closed source services

(Log in to post comments)

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