Subversion Repositories HelenOS-doc

Rev

Rev 129 | Rev 157 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 129 Rev 137
Line 80... Line 80...
80 
          <para>Notification queue</para>
 80 
          <para>Notification queue</para>
81 
        </listitem>
 81 
        </listitem>
82 
      </itemizedlist>
 82 
      </itemizedlist>
83 
 
 83 
 
84 
      <figure float="1">
 84 
      <figure float="1">
- 
 
 85 
        <title>Low level IPC</title>
- 
 
 86 
 
85 
        <mediaobject id="ipc1">
 87 
        <mediaobject id="ipc1">
86 
          <imageobject role="pdf">
 88 
          <imageobject role="pdf">
87 
            <imagedata fileref="images/ipc1.pdf" format="PDF" />
 89 
            <imagedata fileref="images/ipc1.pdf" format="PDF" />
88 
          </imageobject>
 90 
          </imageobject>
89 
 
 91 
 
Line 93... Line 95...
93 
 
 95 
 
94 
          <imageobject role="fop">
 96 
          <imageobject role="fop">
95 
            <imagedata fileref="images/ipc1.svg" format="SVG" />
 97 
            <imagedata fileref="images/ipc1.svg" format="SVG" />
96 
          </imageobject>
 98 
          </imageobject>
97 
        </mediaobject>
 99 
        </mediaobject>
98 
 
 - 
 
99 
        <title>Low level IPC</title>
 - 
 
100 
      </figure>
 100 
      </figure>
101 
 
 101 
 
102 
      <para>The communication between task A, that is connected to task B
 102 
      <para>The communication between task A, that is connected to task B
103 
      looks as follows: Task A sends a message over it's phone to the target
 103 
      looks as follows: Task A sends a message over it's phone to the target
104 
      asnwerbox. The message is saved in task B incoming call queue. When task
 104 
      asnwerbox. The message is saved in task B incoming call queue. When task
Line 228... Line 228...
228 
      messages from the answerbox and puts them into appropriate queues of
 228 
      messages from the answerbox and puts them into appropriate queues of
229 
      running tasks. If a task waiting for a message is not running, the
 229 
      running tasks. If a task waiting for a message is not running, the
230 
      control is transferred to it.</para>
 230 
      control is transferred to it.</para>
231 
 
 231 
 
232 
      <figure float="1">
 232 
      <figure float="1">
- 
 
 233 
        <title>Single point of entry</title>
233 
        <mediaobject id="ipc2">
 234 
        <mediaobject id="ipc2">
234 
          <imageobject role="pdf">
 235 
          <imageobject role="pdf">
235 
            <imagedata fileref="images/ipc2.pdf" format="PDF" />
 236 
            <imagedata fileref="images/ipc2.pdf" format="PDF" />
236 
          </imageobject>
 237 
          </imageobject>
237 
 
 238 
 
Line 242... Line 243...
242 
          <imageobject role="fop">
 243 
          <imageobject role="fop">
243 
            <imagedata fileref="images/ipc2.svg" format="SVG" />
 244 
            <imagedata fileref="images/ipc2.svg" format="SVG" />
244 
          </imageobject>
 245 
          </imageobject>
245 
        </mediaobject>
 246 
        </mediaobject>
246 
 
 247 
 
247 
        <title>Single point of entry</title>
 - 
 
248 
      </figure>
 248 
      </figure>
249 
 
 249 
 
250 
      <para>Very similar situation arises when a task decides to send a lot of
 250 
      <para>Very similar situation arises when a task decides to send a lot of
251 
      messages and reaches kernel limit of asynchronous messages. In such
 251 
      messages and reaches kernel limit of asynchronous messages. In such
252 
      situation 2 remedies are available - the userspace liberary can either
 252 
      situation 2 remedies are available - the userspace liberary can either
Line 268... Line 268...
268 
      kernel limit for outgoing messages is reached, the data is automatically
 268 
      kernel limit for outgoing messages is reached, the data is automatically
269 
      cached within the application. This behaviour is enforced automatically
 269 
      cached within the application. This behaviour is enforced automatically
270 
      and the decision making is hidden from developers view.</para>
 270 
      and the decision making is hidden from developers view.</para>
271 
 
 271 
 
272 
      <figure float="1">
 272 
      <figure float="1">
- 
 
 273 
        <title>Single point of entry solution</title>
273 
        <mediaobject id="ipc3">
 274 
        <mediaobject id="ipc3">
274 
          <imageobject role="pdf">
 275 
          <imageobject role="pdf">
275 
            <imagedata fileref="images/ipc3.pdf" format="PDF" />
 276 
            <imagedata fileref="images/ipc3.pdf" format="PDF" />
276 
          </imageobject>
 277 
          </imageobject>
277 
 
 278 
 
Line 282... Line 283...
282 
          <imageobject role="fop">
 283 
          <imageobject role="fop">
283 
            <imagedata fileref="images/ipc3.svg" format="SVG" />
 284 
            <imagedata fileref="images/ipc3.svg" format="SVG" />
284 
          </imageobject>
 285 
          </imageobject>
285 
        </mediaobject>
 286 
        </mediaobject>
286 
 
 287 
 
287 
        <title>Single point of entry solution</title>
 - 
 
288 
      </figure>
 288 
      </figure>
289 
    </section>
 289 
    </section>
290 
 
 290 
 
291 
    <section>
 291 
    <section>
292 
      <title>Ordering Problem</title>
 292 
      <title>Ordering Problem</title>