practice topics for cs143a final

running to ready is cause by

interrupt

ready to running state is caused by

scheduler dispatch

running to waiting is caused by

i/o or event wait

waiting to ready

i/o or event completion

running to terminated

exit()

block devices

supports random access to data in fixed size blocks

character devices

continuous, unformatted bytes. No random access

progess

if no process is currently executing critical section, only processes not in the remainder section can decide which process to go next

page fault

occurs when process accesses a valid address but page is not in RAM

contiguous allocation

supports random access, files are assigned linear sequential blocks on disk

convoy effect

short processes waiting behind long processes in FCFS scheduling

interrupt vector table

holds the start address of the interrupt table for different types of interrupts

threads share:

virtual address space, code, heap

ready state of a process

when the process is able to continue execution if run on a cpu core

scatter/gather i/o

one system call can perform multiple i/o operations

asynchronous syscall

allows the calling user space program to continue execution while i/o is performed

mmio

creates a one to one mapping between pin voltage and the bits in a register