From 53fb837afc4285486e318bcb614c911bbe9b1348 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Thu, 13 Jan 2000 19:25:15 +0000 Subject: POSIX message queues now include complete functionality including blocking sends when the queue is full. The SuperCore was enhanced to support blocking on send. The existing POSIX API was debugged and numerous test cases were added to psxmsgq01 by Jennifer Averett. SuperCore enhancements and resulting modifications to other APIs were done by Joel. There is one significant point of interpretation for the POSIX API. 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? We decided to unblock all waiting tasks with an EAGAIN error 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 differently. --- cpukit/itron/src/trcv_mbf.c | 2 -- 1 file changed, 2 deletions(-) (limited to 'cpukit/itron/src/trcv_mbf.c') diff --git a/cpukit/itron/src/trcv_mbf.c b/cpukit/itron/src/trcv_mbf.c index a63f2a6748..0b2b89e612 100644 --- a/cpukit/itron/src/trcv_mbf.c +++ b/cpukit/itron/src/trcv_mbf.c @@ -32,7 +32,6 @@ ER trcv_mbf( CORE_message_queue_Status status; boolean wait; Watchdog_Interval interval; - CORE_message_queue_Submit_types core_priority; interval = 0; if (tmout == TMO_POL) { @@ -62,7 +61,6 @@ ER trcv_mbf( msg, p_msgsz, wait, - &core_priority, interval ); _Thread_Enable_dispatch(); -- cgit v1.2.3