From 2cef9771fba2775c07adea5c7544509e7736b8c0 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 13 Jan 2000 19:20:17 +0000 Subject: Added POSIX interpretation subsection and updated status. The message queue manager chapter needs to be updated to reflect completion of the implementation. --- doc/posix_users/message.t | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc/posix_users/message.t') diff --git a/doc/posix_users/message.t b/doc/posix_users/message.t index 78261f978c..5c0b6aed8c 100644 --- a/doc/posix_users/message.t +++ b/doc/posix_users/message.t @@ -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 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 @subsection Opening or Creating a Message Queue -- cgit v1.2.3