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.

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

Notes<br />

Hex Mnemonic Description<br />

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

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

1. If the caller is a task, it may be preempted as a result of this call.<br />

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

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

the copy time in their design, especially when calling from an ISR.<br />

3. q_vsend() sends a message to a variable length message queue. Use<br />

q_send() to send a message to an ordinary queue.<br />

Multiprocessor Considerations<br />

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

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

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_vsend()<br />

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

on another processor node.<br />

1-102 <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!