Re: [RFC] adding aio_readv/writev

[Clement T. Cole]

>>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