From: Mark Brown <bmark@us.ibm.com>
To: aj@suse.de
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: AIO work in librt
Date: Fri, 23 Apr 2004 16:17:00 -0000 [thread overview]
Message-ID: <OF67D3E707.5D3E9681-ON86256E7F.00585495-86256E7F.005975E3@us.ibm.com> (raw)
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?
-------------------
Mark S. Brown
IBM Systems Group, Linux Technology Center
bmark@us.ibm.com
next reply other threads:[~2004-04-23 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 16:17 Mark Brown [this message]
2004-04-23 16:29 ` Ulrich Drepper
2004-04-23 17:09 ` Jakub Jelinek
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=OF67D3E707.5D3E9681-ON86256E7F.00585495-86256E7F.005975E3@us.ibm.com \
--to=bmark@us.ibm.com \
--cc=aj@suse.de \
--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).