OpenRM - RM Library (rmcr.c)

## Index of OpenRM - RM Library

     RMenum rmPipeBarrierCreateCR (RMpipe *toModify, int barrierNumber)

     RMpipe *toModify - a handle to an RMpipe to be modified.
     int barrierNumber - an integer value specifying a barrier number.

(For use with Chromium only) Use this routine to create a named barrier. The barrier is executed by calling rmPipeBarrierExecCR(). Chromium barriers are intended to be used to synchronize execution of OpenGL streams on crservers.

Chromium barriers, when created, require an integer value indicating the number of streams that will be participating in the barrier. This integer value is provided automatically by this routine. Use the routine rmPipeSetCommSize(), prior to calling rmPipeCreateBarrierCR(), to set the number of crservers that will be participating in execution of the barrier.

Chromium barriers, when executed, synchronize execution of OpenGL code in the crservers. They do not block the application code.

This routine returns RM_CHILL upon success. This routine will return RM_WHACKED if the input RMpipe is NULL, or if the size of the communication collective is zero (use rmPipeSetCommSize to set the size of the collective). This routine does not check for creation of duplicate barriers.

librm library source file: rmcr.c

     RMenum rmPipeBarrierExecCR (RMpipe *toUse, int barrierNumber)

     RMpipe *toUse - a handle to an RMpipe to be used.
     int barrierNumber - an integer value specifying a barrier number.

(For use with Chromium only) Use this routine to issue a "barrier execute" command to Chromium. Chromium barriers are intended to be used to synchronize execution of OpenGL streams on crservers.

Chromium barriers, when created, require an integer value indicating the number of streams that will be participating in the barrier. This integer value is provided automatically by this routine. Use the routine rmPipeSetCommSize(), prior to calling rmPipeBarrierCreateCR(), to set the number of crservers that will be participating in execution of the barrier.

Chromium barriers, when executed, synchronize execution of OpenGL code in the crservers. They do not block the application code.

This routine returns RM_CHILL upon success, or RM_WHACKED if the input RMpipe is NULL. This routine does not check for creation of duplicate barriers.

librm library source file: rmcr.c