Skip to Main Content
Operating Systems: Concurrent and Distributed Software Design
book

Operating Systems: Concurrent and Distributed Software Design

by Jean Bacon, Tim Harris
March 2003
Intermediate to advanced content levelIntermediate to advanced
912 pages
27h 17m
English
Pearson Business
Content preview from Operating Systems: Concurrent and Distributed Software Design

27.5. Processes, threads, fibres and concurrency control

As with UNIX, a process can be considered to be a running instance of an executable program. It has a private address space containing its code and data. As it executes, the operating system can allocate it system resources such as semaphores and communications ports. A process must have at least one thread since a thread is the unit of scheduling by the kernel.

A process executing in user mode invokes operating system services by making system calls. Via the familiar trap mechanism (Section 3.3) its mode is changed to system (privileged) as it enters and executes the operating system and is returned to user mode on its return.

Processes are also represented as objects, so are manipulated ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Principles of Concurrent and Distributed Programming, Second Edition

Principles of Concurrent and Distributed Programming, Second Edition

M. Ben-Ari
Operating Systems in Depth

Operating Systems in Depth

Thomas W. Doeppner

Publisher Resources

ISBN: 0321117891Purchase book