Processes and threads

Словарь

English	Значение
operating systems	Software that manages hardware resources and provides services to running programs.
process/ˈprəʊses/	An instance of a program in execution together with its execution state and allocated resources.
states/steɪts/	The possible configurations or conditions of a system at a particular point in its operation.
ready	A scheduling state in which a task can run once it receives processor time.
running	A task state in which its instructions are currently executing on a processor.
blocked/blɒkt/	A task state waiting for an event or resource before it can become ready.
thread	An execution flow with its own execution state that can share a process's resources.
process control block/ˈprəʊses kənˈtrəʊl blɒk/	An operating-system record containing the state and management information associated with a process.
context switch/ˈkɒntekst swɪtʃ/	Saving one task's execution state and restoring another's so the processor can change which task it runs.

English

The first illusion

An operating systems layer turns one processor into many machines. A process is a program in motion: its own address space, registers, open files.
A process lives through five states: new, ready (waiting only for the CPU), running, blocked (waiting on a device), terminated. A thread is an execution flow inside a process — shared space, own stack.

{exercise:uni-cs0701-states}

Практика

A process waiting for disk I/O is —

Сложность 1/5 · 100 монет + небольшой бонус за первое завершение сегодня

English

To suspend a process the OS saves the process control block — registers, program counter, page-table pointer, open files. The context switch is exactly this save-and-restore.
With course timings, saving and restoring $2000$ bytes at $2$ GB/s costs $1$ µs — plus cache pollution. Switching threads skips the address space (shared), so it is the cheaper switch.

{exercise:uni-cs0701-switch}

Практика

Switching threads is cheaper than switching processes because threads —

Сложность 1/5 · 100 монет + небольшой бонус за первое завершение сегодня

English

Process A faults on a page: running to blocked (disk); the scheduler dispatches B; the disk completes; A becomes ready; later running again — the faulting instruction restarts, so no work is lost.
A web server spawns a thread per connection: shared cache, about $50$ µs create-and-switch; as processes, about $500$ µs. Sharing is the thread's point — and unit 7.3's danger.

Example

Blocked is not ready: blocked waits on a device; ready waits only for the CPU.

{exercise:uni-cs0701-thread}

Практика

A crashed thread takes with it —

Сложность 1/5 · 100 монет + небольшой бонус за первое завершение сегодня