POSIX Message Queues
  OCERA Home  /  Download  /  Components  /  Scheduling  /  POSIX Message Queues (0.2-1)
  Training and support
    POSIX Streams

  Resource management
    Generic Scheduler patch
    Preemption+RTLinux patch
    RTLinux API on Linux
    QoS Manager
    Linux/CBS Scheduler

  Scheduling
    Application Scheduler
    TLSF Memory Allocator
    POSIX CPU Clocks
    POSIX Barriers
    POSIX Message Queues
    POSIX Signals
    POSIX Timers
    POSIX Trace
    RTLinux/CBS Scheduler
    RTLinux CC
    GNAT for RTLinux
    RTLinux ide/fs
    RTLinux Java
    RTLinux Terminal
    RTLinux UDP/IP
    Stand-Alone RTLinux
    XtratuM

  Fault-tolerance
    FT Application Monitor
    FT Controller

  Communication
    CANopen device
    CAN/CANopen monitor
    Virtual CAN API
    RT Ethernet Analyzer
    Linux CAN Driver
    ORTE
    CAN model
    Verification of RTOS

POSIX Message Queues

   Description
Keywords: Real-Time, POSIX, communication, IPC
Description: UNIX systems offers several possibilities for interprocess communication: signals, pipes and FIFO queues, shared memory, sockets, etc. In RTLinux, the most flexible one is shared memory, but the programmer has to use alternative synchronisation mechanism to build a safe communication mechanism between process or threads. On the other hand, signals and pipes lack certain flexibility to establish communication channels between process. In order to cover some of these weaknesses, POSIX standard proposes a message passing facility that offers: 1) Protected and synchronised access to the message queue. Access to data stored in the message queue is properly protected against concurrent operations. 2) Prioritised messages. Processes can build several flows over the same queue, and it is ensured that the receiver will pick up the oldest message from the most urgent flow. 3) Asynchronous and temporised operation. Processes have not to wait for operation to be finish, i.e., they can send a message without having to wait for someone to read that message. They also can wait an specified amount of time or nothing at all, if the message queue is full or empty. 4) Asynchronous notification of message arrivals. A receiver process can configure the message queue to be notified on message arrivals. So such a process can be working on something else until the expected message arrives.
   General information
Author(s): Sergio Saez (UPVLC)
Participants: Universidad Politecnica de Valencia
Workpackage: Development of real-time scheduling components (WP5)
Deliverable: Component documentation can be found in deliverable D5.2_rep
Component homepage: http://www.ocera.org
Licenses: MPL, GPL, LGPL and CeCILL (Multiple license issues)
Current version: 0.2-1
Status: Testing
Hardware:
Processor: Independent
Platform:
RTLinux: 3.2pre1
Dependencies: RTLinux(3.2pre1) and PSignals(>=0.2)
   Download
Current version: 0.2-1 [pmqueue-0.2-1.tgz] [src] [CVS at SourceForge]
Previous versions: [0.1]
Note: This component cannot be used directly. It has to be used within OCERA framework. Sources are provided only for documentation and portability purposes.

 Status codes: Analysis >> Design >> Alpha >> Beta >> Testing >> Stable

© OCERA Project. webmaster@ocera.org
Maintained by: Sergio Sáez   Last update: Wed Jan 10 16:56:56 2007