From: "Ulrich Drepper" <drepper@gmail.com>
To: "Benjamin LaHaise" <bcrl@kvack.org>
Cc: "Dan Aloni" <da-x@monatomic.org>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: Status of AIO
Date: Mon, 6 Mar 2006 14:53:07 -0800 [thread overview]
Message-ID: <a36005b50603061453w36f5d49cs7bac0c186aee30b3@mail.gmail.com> (raw)
In-Reply-To: <20060306211854.GM20768@kvack.org>
On 3/6/06, Benjamin LaHaise <bcrl@kvack.org> wrote:
> Socket AIO is not supported yet, but it is useful to get user requests to
> know there is demand for it.
I don't think the POSIX AIO nor the kernel AIO interfaces are suitable
for sockets, at least the way we can expect network traffic to be
handled in the near future. Some more radical approaches are needed.
I'll have some proposals which will be part of the talk I have at OLS.
next prev parent reply other threads:[~2006-03-06 22:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 6:24 Dan Aloni
2006-03-06 15:05 ` Phillip Susi
2006-03-06 21:18 ` Benjamin LaHaise
2006-03-06 22:53 ` Ulrich Drepper [this message]
2006-03-06 23:15 ` Phillip Susi
2006-03-08 7:09 ` Ulrich Drepper
2006-03-08 15:58 ` Phillip Susi
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=a36005b50603061453w36f5d49cs7bac0c186aee30b3@mail.gmail.com \
--to=drepper@gmail.com \
--cc=bcrl@kvack.org \
--cc=da-x@monatomic.org \
--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 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®