From: "Clement T. Cole" <clemc@alumni.cmu.edu>
To: Shailabh Nagar <nagar@watson.ibm.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Benjamin LaHaise <bcrl@redhat.com>,
Andrew Morton <akpm@digeo.com>,
Alexander Viro <viro@math.psu.edu>,
linux-aio <linux-aio@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] adding aio_readv/writev
Date: Mon, 23 Sep 2002 16:39:42 -0400 [thread overview]
Message-ID: <20020923203238Z261292-8740+66@vger.kernel.org> (raw)
In-Reply-To: Your message of "Mon, 23 Sep 2002 15:52:21 EDT." <3D8F70F5.4040406@watson.ibm.com>
>>It would have been nice to have corresponding data for the async path.
Agreed... I'll let you know if I learn anything. When Richard wrote
APUE, aio was not defined by Posix. Only the select/poll and turning
on the O_*SYNC flags hacks from BSD and SVR4. I don't think you will
learn much from that.
As I said, many/most of the commerical Un*x folks added their own
propritary (and slightly different) version of aio years ago. Then
they agreed on the Posix interface and most [if not all] have offered
those. Most of the majpr ISV's that used their proprietary ones
have switched to or are in the process of switching too the Posi
interface for simpliticy [if they could - there are sometimes reasons
why they can not - not always technical reasons BTW].
I personally started to monitor this mailing list because I was
interested in Ben's work on aio for Linux and what I'm researching
needs to be follow what Linux is doing in this area.
For what ever its worth to this list: I have local implementations
of the Posix async I/O for a Sun and *BSD. I trying to get my hands
on a Alpha and SVR5 [<-- bits secured for the later but no HW at
the moment to try it]. If you have any aio test cases, let me know.
As I do my research, if I can learn anything useful I'll be willing
to pass it on if you think it will help.
I'm currently thinking up/trying some examples and there are some
worrisome issues with the Posix spec IMHO. I know that you
folks are not trying to be Posix compliant - which is both
a blessing and curse.
In my case, I need to follow Posix, since that's
what the ISVs really use as their guide. My assumption is that
there will be mapping layer between your final interface and
the Posix interface. I can offer any extensions as need/appropriate if
I can show that it helps [which in this case it might].
Clem
next prev parent reply other threads:[~2002-09-23 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200209231851.g8NIpea12782@igw2.watson.ibm.com>
2002-09-23 19:52 ` [RFC] adding aio_readv/writev Shailabh Nagar
2002-09-23 20:39 ` Clement T. Cole [this message]
2002-09-23 17:59 Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 20:39 Shailabh Nagar
[not found] ` <1032555981.2082.10.camel@dell_ss3.pdx.osdl.net>
2002-09-23 14:30 ` Shailabh Nagar
2002-09-23 18:53 ` Clement T. Cole
[not found] ` <20020923114104.A11680@redhat.com>
2002-09-24 13:20 ` John Gardiner Myers
2002-09-24 13:52 ` Stephen C. Tweedie
2002-09-24 14:13 ` John Gardiner Myers
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=20020923203238Z261292-8740+66@vger.kernel.org \
--to=clemc@alumni.cmu.edu \
--cc=akpm@digeo.com \
--cc=bcrl@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nagar@watson.ibm.com \
--cc=shemminger@osdl.org \
--cc=viro@math.psu.edu \
/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 NNTP newsgroup(s).