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

2.6. Operating system structure

Early operating systems were monolithic or unstructured, as were those for PCs until very recently. Such systems run without a privilege boundary, and arbitrary procedure calls, reads and writes can take place. The first step in providing structure is to use the hardware protection boundary to make the operating system privileged and applications unprivileged. The system calls can then be the hardware-enforced operating system interface to applications.

An operating system is a very large piece of software; for example, Sun's UNIX kernel (the basic functions described above and shown in Figure 2.13) occupies over a megabyte. Figure 2.13 shows some of the internal modules in a conventional closed operating system, ...

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