The XidarML daemon task object. Poll the high priority command queue, and having drained it, walk the device list looking for low priority requests. Source: ../mld.c.html#TML
The daemon scans its high priority queue for messages. The first token of any resulting command string is inspected. If the token is "MLDoNode", a device name is read off the command string and the deamon proceeds to satisfy all requests to talk to that device.If the first token isn't "MLDoNode, then the token is taken to be a function name and the function is called with this bus object as the first argument and with a pointer to the rest of the command string as the second argument.
When the high priority command queue is exhausted, the daemon resumes working through the list of all nodes for this bus in "path" order. Any task may request control of the bus by pending on the semaphore of the node it is interested in. When the daemon visits the branch of the net that contains a particular node, any task pending on that node get control of the bus. This way a minimum amount of time is spent activating and deactivating branching switches and maximum throughput is achieved.
Copyright © 1996
Eliot W. Dudley
All rights reserved.
|
generated by doc++