06.08.2013 Views

pSOSystem System Calls - Read

pSOSystem System Calls - Read

pSOSystem System Calls - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

q_avsend pSOS+ <strong>System</strong> <strong>Calls</strong><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 provided, 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 send a message asynchronously 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 />

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

kernel will ready the task and give it the relayed message. Thus, a q_avsend()<br />

call, whether it is on the local or a remote queue, may cause pSOS+m activities<br />

on another processor node.<br />

1-66 <strong>pSO<strong>System</strong></strong> <strong>System</strong> <strong>Calls</strong>

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

Saved successfully!

Ooh no, something went wrong!