public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Miell <nmiell@comcast.net>
To: Dan Aloni <da-x@monatomic.org>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Status of AIO
Date: Mon, 06 Mar 2006 17:37:13 -0800	[thread overview]
Message-ID: <1141695433.2993.5.camel@entropy> (raw)
In-Reply-To: <20060307013049.GA19775@localdomain>

On Tue, 2006-03-07 at 03:30 +0200, Dan Aloni wrote:
> On Mon, Mar 06, 2006 at 04:18:54PM -0500, Benjamin LaHaise wrote:
> > On Mon, Mar 06, 2006 at 08:24:03AM +0200, Dan Aloni wrote:
> > > Hello,
> > > 
> > > I'm trying to assert the status of AIO under the current version 
> > > of Linux 2.6. However by searching I wasn't able to find any 
> > > indication about it's current state. Is there anyone using it
> > > under a production environment?
> > 
> > For O_DIRECT aio things are pretty stable (barring a patch to improve -EIO 
> > handling).  The functionality is used by the various databases, so it gets 
> > a fair amount of exercise.
> > 
> > > I'd like to know how complete it is and whether socket AIO is
> > > adaquately supported.
> > 
> > Socket AIO is not supported yet, but it is useful to get user requests to 
> > know there is demand for it.
> 
> Well, I've written a small test app to see if it works with network
> sockets and apparently it did for that small test case (connect() 
> with aio_read(), loop with aio_error(), and aio_return()). I thought 
> perhaps the glibc implementation was running behind the scene, so I've 
> checked to see if it a thread was created in the background and I 
> there wasn't any thread. 

None of the aio_* functions use the kernel's AIO interface. They're
implemented entirely in userspace using a thread pool.

-- 
Nicholas Miell <nmiell@comcast.net>


  reply	other threads:[~2006-03-07  1:37 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
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 [this message]
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=1141695433.2993.5.camel@entropy \
    --to=nmiell@comcast.net \
    --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