From: Christopher Smith <x@xman.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: bert hubert <bert.hubert@netherlabs.nl>,
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, 04 Feb 2007 22:46:25 -0800 [thread overview]
Message-ID: <45C6D2C1.5010103@xman.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702041548480.18633@alien.or.mcafeemobile.com>
Davide Libenzi wrote:
> 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.
>
SGI's kaio patch to linux kind of went that route (using kthreads) for
non-SCSI async IO. It wasn't a bad way to go, but at least for
disk-based access they achieved much better results when they could go
right to the hardware.
--Chris
prev parent reply other threads:[~2007-02-05 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-04 22:55 regarding generic AIO, async syscalls precedent + some benchmarks by lighttpd bert hubert
2007-02-05 0:15 ` Davide Libenzi
2007-02-05 6:46 ` Christopher Smith [this message]
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=45C6D2C1.5010103@xman.org \
--to=x@xman.org \
--cc=bcrl@kvack.org \
--cc=bert.hubert@netherlabs.nl \
--cc=davidel@xmailserver.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.