From: Benjamin LaHaise <bcrl@redhat.com>
To: marco <marco@tux.dynu.com>
Cc: suparna@in.ibm.com, linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: Kernel support of socket async I/O
Date: Mon, 25 Feb 2002 14:20:14 -0500 [thread overview]
Message-ID: <20020225142013.E11675@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0202251521440.27334-100000@valeria.casa>
In-Reply-To: <Pine.LNX.4.21.0202251521440.27334-100000@valeria.casa>; from marco@tux.dynu.com on Mon, Feb 25, 2002 at 05:05:41PM +0100
On Mon, Feb 25, 2002 at 05:05:41PM +0100, marco wrote:
> Hello Benjamin and all of the guys on the lists,
> I'm pretty much interested in socket async I/O for a project at work. I
> read the document at
...
> I also searched linux-kernel archives for some status information, but
> couldn't gain much info (other than a couple of discussion threads back in
> late 1999).
> What we need is a standard aio/thread-pool-in-sigwaitinfo architecture and
> we wouldn't like to use select/poll.
...
Recent development activity was mostly geared at raw block device and
filesystem aio (as that's what the testers are using). I did post patches
for network aio, but dropped them due to time constraints. Now that the
most recent flurry of fixes to the aio core is complete (it's looking
very good now), I need to get the core bits updated for 2.5 and see how
much can be merged. As for help, the network bits need polish and testing
to get to the near-release quality of the rest of the code.
-ben
next prev parent reply other threads:[~2002-02-25 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 16:05 Kernel support of socket async I/O marco
2002-02-25 19:20 ` Benjamin LaHaise [this message]
2002-02-25 21:16 ` marco
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=20020225142013.E11675@redhat.com \
--to=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco@tux.dynu.com \
--cc=suparna@in.ibm.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.