• threads share data and variables through their common search path different stacks, same "global" address space.
  • similar to exec but share data, etc. and easier for inter-communication
  • manager governing the behaviour of all threads
  • like client-server. Server includes main thread governing all the others and a signal thread. Each evaluator thread is a client.
  • evaluator manager keep track of statistics for use in time on CPU, complete elapsed time, etc. for each thread
  • threads should have names in their ids.
  • different approaches to threads - native S threads, Pthreads. One evaluator switching between expressions (problem of recursion and reinstating the stack) and the kernel/OS/library doing the C level context switch.
    Pros and cons of each.
  • extension to multi-processors. What is involved. Single global Eval structure.
    Last modified: Wed Feb 5 09:27:12 1997