mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: Zach Brown <zach.brown@oracle.com>,
	Benjamin LaHaise <bcrl@kvack.org>, Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-aio@kvack.org, Suparna Bhattacharya <suparna@in.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: regarding generic AIO, async syscalls precedent + some benchmarks by lighttpd
Date: Sun, 4 Feb 2007 16:15:15 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702041548480.18633@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <20070204225541.GA18359@outpost.ds9a.nl>

On Sun, 4 Feb 2007, bert hubert wrote:

> >From two comments posted to my "blog"
> http://blog.netherlabs.nl/articles/2007/02/04/a-synchronous-programming
> 
> Excerpted from the diary of Dragonfly BSD,
> http://www.dragonflybsd.org/status/diary.shtml 
> 
>  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
> http://leaf.dragonflybsd.org/mailarchive/commits/2004-08/msg00067.html
> 
> Comment by Jan Kneschke, lighttpd developer, noting the lack of and need for
> aio_stat():
> 
>  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 http://www.lighttpd.net/benchmark/
>  you can see the impact of async vs. blocking syscalls.
> 
> Perhaps relevant.

Yes, that is some very interesting data IMO. I did not bench the GUASI 
(userspace async thread library) against AIO, but those numbers show that a 
*userspace* async syscall wrapper interface performs in the ballpark of AIO.
This leads to some hope about the ability to effectively deploy the kernel 
generic async AIO (being it fibril or kthreads based) as low-impact async 
provider for basically anything.



- Davide



  reply	other threads:[~2007-02-05  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-04 22:55 bert hubert
2007-02-05  0:15 ` Davide Libenzi [this message]
2007-02-05  6:46   ` Christopher Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0702041548480.18633@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=bcrl@kvack.org \
    --cc=bert.hubert@netherlabs.nl \
    --cc=linux-aio@kvack.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suparna@in.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=zach.brown@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®