<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="QNX - Page 19 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=QNX&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=QNX&amp;p=20">3.Next</a>
</p>
<p>is copied, by the kernel, from the address space of the sending process to that of the receiving process. If the receiving process is waiting for the message, control of the CPU is transferred at the same time, without a pass through the CPU scheduler. Thus, sending a message to another process and waiting for a reply does not result in "losing one's turn" for the CPU. This tight integration between message passing and CPU scheduling is one of the key mechanisms that makes QNX message passing broadly usable. Most <a href="page.php?w=Unix">Unix</a></p><p>
<a accesskey="1" href="page.php?w=QNX&amp;p=18">1.Previous</a><br />
<a accesskey="3" href="page.php?w=QNX&amp;p=20">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
