From: Ulrich Drepper <drepper@redhat.com>
To: bmark@us.ibm.com
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: AIO work in librt
Date: Fri, 23 Apr 2004 16:29:00 -0000 [thread overview]
Message-ID: <4089444B.2060906@redhat.com> (raw)
In-Reply-To: <OF67D3E707.5D3E9681-ON86256E7F.00585495-86256E7F.005975E3@us.ibm.com>
Mark Brown wrote:
> We are thinking about making this work in librt (and submitting it, of
> course).
Making what work? RHEL ships with some support for kernel aio already.
This code (or more specifically: the kernel side) is not yet in
sufficient shape to be accepted. That's what's keeping it back. The
librt side should be done for the current kernel aio approach which is
everything but sane.
So the task is to design an implement a workable aio implementation in
the kernel and I haven't seen anything like this lately.
--
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
next prev parent reply other threads:[~2004-04-23 16:29 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 [this message]
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=4089444B.2060906@redhat.com \
--to=drepper@redhat.com \
--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).