public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Mark Brown <bmark@us.ibm.com>
Cc: aj@suse.de, Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: AIO work in librt
Date: Fri, 23 Apr 2004 17:09:00 -0000	[thread overview]
Message-ID: <20040423145724.GM5191@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <OF67D3E707.5D3E9681-ON86256E7F.00585495-86256E7F.005975E3@us.ibm.com>

On Fri, Apr 23, 2004 at 11:17:09AM -0500, Mark Brown wrote:
> Given this conversation from last year:
> 
> Andreas Jaeger wrote:
> > Ulrich Drepper <drepper at redhat dot com> writes:
> > > Andreas Jaeger wrote:
> > >> AFAIK Ben's kernel level implementation is in current 2.5 kernels.
> > >> Can we base now a glibc implementation on this?  Anybody already
> > >> working on this?
> > >
> > > I doN't think the kernel side is complete enough.
> > 
> > Ben, what is still missing on the kernel side?  Looking at fs/aio.c I
> > thought it was complete.
> 
> We are thinking about making this work in librt (and submitting it, of 
> course).
> Andreas, did you learn anything from Ben? Anyone else know of a
> factor that keeps this from being able to work?

RHEL glibc already includes the rtkaio glibc add-on which is librt using
the kernel AIO interface.
Unfortunately, the kernel side is very limited and doesn't have good
support for the things userland POSIX AIO needs (e.g. in the area of
notification and cancellation, or that many things are serialized in
the kernel rather than truely asynchronous; and from what I've heard
the 2.6 aio is even in worse shape than what we used to have in 2.4.x RHEL
kernels).

	Jakub

  parent reply	other threads:[~2004-04-23 17:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 16:17 Mark Brown
2004-04-23 16:29 ` Ulrich Drepper
2004-04-23 17:09 ` Jakub Jelinek [this message]
2004-04-23 18:21   ` Mark Brown

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=20040423145724.GM5191@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=aj@suse.de \
    --cc=bmark@us.ibm.com \
    --cc=libc-hacker@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).