Changes between Initial Version and Version 1 of Projects/POSIX_Asynchronous_IO


Ignore:
Timestamp:
01/26/10 03:17:45 (13 years ago)
Author:
JoelSherrill
Comment:

New page

Legend:

Unmodified
Added
Removed
Modified
  • Projects/POSIX_Asynchronous_IO

    v1 v1  
     1= POSIX Asynchronous IO =
     2
     3
     4
     5[[TOC(Projects/POSIX_Asynchronous_IO, depth=2)]]
     6
     7
     8'''Status:''' No active volunteers.
     9
     10RTEMS does not currently support POSIX Asynchronous IO as defined by
     11OpenGroup.  These methods and associated constants are prototyped by
     12the [http://www.opengroup.org/onlinepubs/009695399/basedefs/aio.h.html
     13<aio.h>] header file which is ''cpukit/posix/include/aio.h'' in the
     14RTEMS source tree.  The following methods would have to be implemented:
     15
     16 *  [http://www.opengroup.org/onlinepubs/009695399/functions/aio_read.html aio_read()]
     17 *  [http://www.opengroup.org/onlinepubs/009695399/functions/aio_write.html aio_write()]
     18 *  [http://www.opengroup.org/onlinepubs/009695399/functions/aio_cancel.html aio_cancel()]
     19 *  [http://www.opengroup.org/onlinepubs/009695399/functions/aio_error.html aio_error()]
     20 *  [http://www.opengroup.org/onlinepubs/009695399/functions/aio_return.html aio_return()]
     21 *  [http://www.opengroup.org/onlinepubs/009695399/functions/lio_listio.html lio_listio()]
     22
     23All methods currently are implemented in RTEMS as stubs which return ENOSYS.
     24
     25It is assumed that the implementation would have to have one or more
     26server threads and these methods would interact with that server thread
     27by enqueueing operation requests and checking on the completion status.
     28The number of server threads along with characteristics such as stack
     29size and priority would need to be application configurable.