| 81,6 → 81,24 |
|---|
| </listitem> |
| </itemizedlist> |
| |
| <figure float="1"> |
| <mediaobject id="ipc1"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images/ipc1.pdf" format="PDF" /> |
| </imageobject> |
| |
| <imageobject role="html"> |
| <imagedata fileref="images/ipc1.png" format="PNG" /> |
| </imageobject> |
| |
| <imageobject role="fop"> |
| <imagedata fileref="images/ipc1.svg" format="SVG" /> |
| </imageobject> |
| </mediaobject> |
| |
| <title>Low level IPC</title> |
| </figure> |
| |
| <para>The communication between task A, that is connected to task B |
| looks as follows: Task A sends a message over it's phone to the target |
| asnwerbox. The message is saved in task B incoming call queue. When task |
| 211,6 → 229,25 |
|---|
| running tasks. If a task waiting for a message is not running, the |
| control is transferred to it.</para> |
| |
| <figure float="1"> |
| <mediaobject id="ipc2"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images/ipc2.pdf" format="PDF" /> |
| </imageobject> |
| |
| <imageobject role="html"> |
| <imagedata fileref="images/ipc2.png" format="PNG" /> |
| </imageobject> |
| |
| <imageobject role="fop"> |
| <imagedata fileref="images/ipc2.svg" format="SVG" /> |
| </imageobject> |
| </mediaobject> |
| |
| <title>Single point of entry</title> |
| </figure> |
| |
| |
| <para>Very similar situation arises when a task decides to send a lot of |
| messages and reaches kernel limit of asynchronous messages. In such |
| situation 2 remedies are available - the userspace liberary can either |