06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

pSOS+ <strong>System</strong> <strong>Calls</strong> q_avurgent<br />

Notes<br />

Hex Mnemonic Description<br />

0x31 ERR_MSGSIZ Message too large.<br />

0x35 ERR_QFULL Message queue at length limit.<br />

0x3B ERR_NOTVARQ Queue is not variable length.<br />

0x65 ERR_STALEID Object's node has failed.<br />

If an MC_ASYNCERR routine is not present, the pSOS+m kernel generates a fatal<br />

error.<br />

1. This call is supported only by the pSOS+m kernel.<br />

2. The calling task can be preempted as a result of this call.<br />

3. The pSOS+m kernel must copy the message into a queue buffer or the receiving<br />

task's buffer. Longer messages take longer to copy. Users should account for the<br />

copy time in their designs.<br />

4. q_avsend() asynchronously sends a message to a variable length message<br />

queue. Use q_asend() to asynchronously send a message to an ordinary<br />

message queue.<br />

Multiprocessor Considerations<br />

1. If qid identifies a global queue residing on another processor node, then the<br />

pSOS+m kernel will internally make an RSC to that remote node to post the<br />

input message to that queue.<br />

2. If a task awakened by this call does not reside on the local node, the local kernel<br />

internally passes the message to the task's node of residence, whose pSOS+m<br />

kernel readies the task and gives it the relayed message. Thus, a<br />

q_avurgent() call, whether it is on the local or a remote queue, can cause<br />

pSOS+m activity on another processor node.<br />

<strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong> 1-69<br />

1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!