Class Fifo_mode that determines the mode of a fifo from the user's point of view.
Class Fifo_mode that determines the mode of a fifo from the user's point of view. Internally to the DD system it hides the details of the structure sFifo_mode from the user.The reason for having Fifo_mode and the above mentioned structure sFifo_mode (defined in fifo.h) is that we do want to give the user all the advantages of a class, but we also want to have the fifos (which reside in shared memory) in the simplest possible form, hence the use of a structure.
The Fifo_mode has the following options:
- Fill_mode: Determines how the fifo is being filled, i.e.
fill_all: every event is put into this fifo,
fill_onreq: an event is only put into this fifo if a process is waiting for such an event
fill_reqcnt: Put the event into the fifo if the count of the fifo is below the request count (see below)
fill_prescaled: Put the event into the fifo if it is properly prescaled- filter: Determines whether we filter the events according to the control words
filter_on: filter is on,
filter_off: no filter (i.e. no event selection)- eWait: wait mode that determines what happens when a process is trying to read an empty fifo,
sleep_mode: process falls asleep and wakes up when an event arrives
async_mode: process returns with an error status- iPrescale: integer that determines the prescale factor of the fifo
- iReqcnt: integer that determines the request count (i.e. an event is always put into this fifo if it has fewer than iReqcnt events in it).
- eSuser: Single user mode:
multi_user: several processes are allowed to read from this fifo
single_user: only one process is allowed to read from the fifo- fctl: control words that determine the filter (see the section on the event distribution for details).
Modifications:
Alphabetic index HTML hierarchy of classes or Java