CS452 - Real-Time Programming - Fall 2008

Lecture 17 - Serial Hardware


Questions & Comment

  1. out 2

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. Courier
  3. Server

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 before courier and server.

  1. Notifier
  2. Buffer
  3. Courier
  4. Server

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: