Masatake, On Thu, Jun 19, 2008 at 4:48 AM, Masatake YAMATO <[EMAIL PROTECTED]> wrote: >> And the text I'll add to each page is something like this: >> >> RETURN VALUE >> On success, io_cancel() returns 0. For the failure >> return, see NOTES. >> >> NOTES >> Glibc does not provide a wrapper function for this system >> call. >> >> The wrapper provided in libaio for io_cancel() does not >> follow the usual C library conventions for indicating >> error: on error it returns a negated error number (the >> negative of one of the values listed in ERRORS). If the >> system call is invoked via syscall(2), then the return >> value follows the usual conventions for indicating an >> error: -1, with errno set to a (positive) value that >> indicates the error. > > Really good. I have learnt many your discussion. > Thank you. > >>>>> io_setup >>>>> io_getevents >>>>> io_submit >>>>> io_destroy >>>>> io_cancel > > How about other system calls than io_cancel? > I'll write test cases for them based on your man page.
I'm not sure how much the man pages will help == some of the io_* man pages seem rather thin on details. > I wonder the NOTES are applicable to the other system call. Yes, I have added similar text to all of the io_* pages. It will be in man-pages-3.01. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
