public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
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 20:37:31 -0500	[thread overview]
Message-ID: <440CE3DB.5050103@cfl.rr.com> (raw)
In-Reply-To: <20060307013049.GA19775@localdomain>

aio_* functions are library routines in glibc that are implemented by 
spawning threads to use the normal kernel io syscalls.  They don't use 
real async IO in the kernel.  I'm not sure why you didn't see the 
thread, but if you look up the glibc sources you will see how it works.

To use the kernel aio you make calls to io_submit().

Dan Aloni wrote:
> 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. 
> 


  parent reply	other threads:[~2006-03-07  1:38 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
2006-03-07  1:37     ` Phillip Susi [this message]
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=440CE3DB.5050103@cfl.rr.com \
    --to=psusi@cfl.rr.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