CS452 - Real-Time Programming - Spring 2008

Lecture 24 - Task Structure


Questions & Comment

  1. Kernel assignment
  2. out2 needs to be set
  3. edge versus level-triggered at the input to the ICU

Task Structure

Server Notifier Buffer Courier

1. Simplest

  1. Notifier
  2. Server

Remember that all the calls provide error returns. You can/should use them for error recovery

2 Using a Courier

Simplest is best

  1. Notifier
  2. Server
  3. Courier

This gets you through a bottleneck where no more than two events come too fast.

Remember that all the calls provide error returns. You can/should use them for error recovery

3. Buffering

Add buffer & courier between courier and server.

  1. Buffer

This structure clears up problems when the notifier runs too fast for the server.

Two issues:

  1. Handles bottlenecks of all sizes.

    Define `bottleneck'.

  2. Server could be buffered on the other side

    Called a guard.

What this amounts to is

Administrator, Worker


Return to: