Added POSIX interpretation subsection and updated status.

The message queue manager chapter needs to be updated to reflect
completion of the implementation.
This commit is contained in:
Joel Sherrill
2000-01-13 19:20:17 +00:00
parent 9c1c778d56
commit 2cef9771fb
2 changed files with 16 additions and 4 deletions

View File

@@ -123,6 +123,21 @@ by passing a NULL to mq_notify, this removes any notification request
attached to the queue. Whenever the message queue is closed, all attached to the queue. Whenever the message queue is closed, all
notification attachments are removed. notification attachments are removed.
@subsection POSIX Interpretation Issues
There is one significant point of interpretation related to
the RTEMS implementation of POSIX message queues:
@cite{What happens to threads already blocked on a message queue when the
mode of that same message queue is changed from blocking to non-blocking?}
The RTEMS POSIX implementation decided to unblock all waiting tasks
with an @code{EAGAIN} status just as if a non-blocking version of
the same operation had returned unsatisfied. This case is not
discussed in the POSIX standard and other implementations may have
chosen alternative behaviors.
@section Operations @section Operations
@subsection Opening or Creating a Message Queue @subsection Opening or Creating a Message Queue

View File

@@ -26,7 +26,6 @@ when porting existing code from UNIX to RTEMS.
@item The current implementation of @code{dup()} is insufficient. @item The current implementation of @code{dup()} is insufficient.
@item FIFOs @code{mkfifo()} are not currently implemented. @item FIFOs @code{mkfifo()} are not currently implemented.
@item Asynchronous IO is not implemented. @item Asynchronous IO is not implemented.
@item Blocking Send for Message Queues is not implemented
@item The @code{flockfile()} family is not implemented @item The @code{flockfile()} family is not implemented
@item getc/putc unlocked family is not implemented @item getc/putc unlocked family is not implemented
@item Shared Memory is not implemented @item Shared Memory is not implemented
@@ -41,8 +40,6 @@ level of support is appropriate and possible for RTEMS.
@item Functional Testing @item Functional Testing
@itemize @bullet @itemize @bullet
@item Named Semaphores are untested.
@item There is currently no Message Queue test.
@item Tests for unimplemented services @item Tests for unimplemented services
@end itemize @end itemize
@@ -53,7 +50,7 @@ level of support is appropriate and possible for RTEMS.
@item Documentation @item Documentation
@itemize @bullet @itemize @bullet
@item Many of the service description pages are completed in this @item Many of the service description pages are not complete in this
manual. These need to be completed and information added to the manual. These need to be completed and information added to the
background and operations sections. background and operations sections.
@item Example programs (not just tests) would be very nice. @item Example programs (not just tests) would be very nice.