- Operating Systems: Three Easy Pieces - University of Wisconsin–Madison
The book is centered around three conceptual pieces that are fundamental to operating systems: virtualization, concurrency, and persistence In understanding the conceptual, you will also learn the practical, including how an operating system does things like schedule the CPU, manage memory, and store files persistently
- 致本书读者 - University of Wisconsin–Madison
名为《Operating Systems:Three Easy Pieces》，这显然是向理查德·费曼（Richard Feynman） 针对物理学主题创作的、最了不起的一套讲义[F96]致敬。 虽然本书不能达到这位著名物理
- Preface - University of Wisconsin–Madison
operating systems (and more generally, systems) are all about The three easy pieces refer to the three major thematic elements the book is organized around: virtualization, concurrency, and persistence In discussing these concepts, we’ll end up discussing most of the impor-tant things an operating system does; hopefully, you’ll also have some
- 1 关于本书的对话 - University of Wisconsin–Madison
教授：欢迎阅读这本书，本书英文书名为《Operating Systems:Three Easy Pieces》，由我 来讲授关于操作系统的知识。请做一下自我介绍。 学生：教授，您好，我是学生，您可能已经猜到了，我已经准备好开始学习了！ 教授：很好。有问题吗？ 学生：有！
- Operating Systems: Three Easy Pieces
Operating Systems: Three Easy Pieces Errata and Book News Here is a list of problems found and fixed in the book, as well as book news Thanks so much to all of you for your help! Check out the book preface for more specific acknowledgements
- A Dialogue on the Book - University of Wisconsin–Madison
we’re going to do Three Easy Pieces on the fine topic of Operating Systems This is appropriate, as Operating Systems are about half as hard as Physics Student: Well, I liked physics, so that is probably good What are those pieces? Professor: They are the three key ideas we’re going to learn about: virtualiza-tion, concurrency, and
- Homework - University of Wisconsin–Madison
Some homeworks are just short programming exercises, allowing you to explore how real systems work For the simulators, the basic idea is simple: each of the simulators below let you both generate problems and obtain solutions for an infinite number of problems
- The Abstraction: The Process - University of Wisconsin–Madison
In many operating systems, a common design paradigm is to separate high-level policies from their low-level mechanisms [L+75] You can think of the mechanism as providing the answer to a how question about a system; for example, how does an operating system perform a context switch? The policy provides the answer to a which question; for example,
|