Re: aio manuals

[Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>]

"Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> On Tue, May 8, 2012 at 1:44 AM, Jeff Moyer <jmoyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> On Thu, Oct 13, 2011 at 9:29 PM, Cyril Hrubis <chrubis-AlSwsSmVLrQ@public.gmane.org> wrote:
>>>> Hi!
>>>>> > > So should we settle for memset()? I could update send updated patch
>>>>> > > then.
>>>>> >
>>>>> > Yeah, memset is what I typically have done.
>>>>> >
>>>>>
>>>>> Here comes updated patch.
>>>>
>>>> I've checked the latest man pages git and these changes aren't there
>>>> yet. Any comments?
>>>
>>> So, I'm struggling. What is the relationship between the io_*()
>>> functions in libaio and the io_*() syscalls?
>>
>> The io_* library calls are wrappers around the system calls.  In some
>> cases, the wrappers simply pass the arguments on to the system call.  In
>> other cases, there is some work performed by the library.
>>
>>> The page was attempting to document the system calls, which use
>>> aio_context_t structures,
>>
>> Well, aio_context_t is not a structure, it's just an unsigned long.
>>
>> I guess that we'll ultimately need the io_* syscalls documented in
>> chapter 2, and the library function documented in chapter 3, right?
>
> Jeff,
>
> Quick question: where is the canonical home of libaio? It's not easy
> to find. I'd like to ensure I'l looking at the latest sources, ideally
> by pulling from a VCS.

http://git.fedorahosted.org/git/?p=libaio.git

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html