From: Phillip Susi <psusi@cfl.rr.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>, Dan Aloni <da-x@monatomic.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Status of AIO
Date: Wed, 08 Mar 2006 10:58:00 -0500 [thread overview]
Message-ID: <440EFF08.3040604@cfl.rr.com> (raw)
In-Reply-To: <a36005b50603072309w3b622edek5c6c2e7b59d7b2d5@mail.gmail.com>
Ulrich Drepper wrote:
> What has network I/O to do with O_DIRECT? I'm talking about async network I/O.
O_DIRECT allows for zero copy IO, which saves a boatload of cpu cycles.
For disk IO it is possible to use O_DIRECT without aio, but there is
generally a loss of efficiency doing so. For network IO, O_DIRECT is
not even possible without aio.
By using aio and O_DIRECT for network IO, you can achieve massive
performance and scalability gains.
You said before that the kernel aio interface is not suitable for
sockets. Why not?
next prev parent reply other threads:[~2006-03-08 15:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 6:24 Status of AIO Dan Aloni
2006-03-06 15:05 ` Phillip Susi
2006-03-06 21:18 ` Benjamin LaHaise
2006-03-06 22:53 ` Ulrich Drepper
2006-03-06 23:15 ` Phillip Susi
2006-03-08 7:09 ` Ulrich Drepper
2006-03-08 15:58 ` Phillip Susi [this message]
2006-03-06 23:33 ` Benjamin LaHaise
2006-03-07 0:24 ` David S. Miller
2006-03-07 0:42 ` Benjamin LaHaise
2006-03-07 0:51 ` David S. Miller
2006-03-07 1:39 ` Benjamin LaHaise
2006-03-07 2:04 ` Dan Aloni
2006-03-07 2:07 ` Benjamin LaHaise
2006-03-07 3:11 ` David S. Miller
2006-03-07 7:33 ` Dan Aloni
2006-03-07 3:06 ` David S. Miller
2006-03-07 16:35 ` Benjamin LaHaise
2006-03-07 1:34 ` Phillip Susi
2006-03-07 3:04 ` David S. Miller
2006-03-07 4:07 ` Phillip Susi
2006-03-07 6:02 ` David S. Miller
2006-03-07 16:06 ` Phillip Susi
2006-03-07 1:30 ` Dan Aloni
2006-03-07 1:37 ` Nicholas Miell
2006-03-07 1:37 ` Phillip Susi
2006-03-07 1:40 ` Benjamin LaHaise
2006-03-06 23:18 ` Phillip Susi
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=440EFF08.3040604@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=bcrl@kvack.org \
--cc=da-x@monatomic.org \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.