Advanced Operating Systems   COMP9242 2002/S2

UNSW

Printer-Friendly Version Administration                - Notices - Course Intro - Consultations # On-line Survey (closed) - Survey Results   Work - Lectures - Milestone 0 - Project Admin - Project Spec - Project FAQ - Exam   Documentation - ASysT Lab - L4 source browser - Sulima ISA Simulator - R4x00 ISA Summary  - MIPS R4700 Reference - MIPS R4000 User Manual  - Network Driver - GT64111   Related Info - Aurema OS Prize - OS Hall of Fame   History - 2000 - 1999 - 1998   Staff - Gernot Heiser (LiC)

Tasks A task essentially provides an address space (plus a clan boundary). An (active) task contains one or more (active) threads. The number of threads in a task is fixed (128 on R4k). Upon task creation, the full set of (128) threads is created with the task, all but one are inactive (i.e., they do nothing and consume no resources). further threads can be activated via a system call (lthread_ex_regs()) Model will change in future versions! Similarly, upon system initialisation, the full set of tasks (2048 on R4k) is created, but in an inactive state. A task has a chief (parent/owner). Chiefs will vanish in future versions! .