operating system
What you see is temporary, what you don't see is forever.
When you are playing games, chatting with friends or writing a program and loading and running on your computer, do you feel like watching magic? The written program can be compiled and run, the result calculated, and displayed or printed out. Do you think it is mysterious?
If you want to unveil this mystery, you have to learn the operating system.
Because the operating system is the system that controls the operation of the computer, in the process of learning it, readers can understand the panorama of the program running on the computer, or what we think of as the panorama. I say this because it is extremely difficult to accurately understand the panorama of the program running on the computer (some people think this is simply impossible). Of course, the program here refers to a program with a certain scale, not a trivial program with a few lines of code. To some extent, no one is sure that they know the state of the computer at any moment. For example, on a multi-pipeline computer, if an interruption or exception occurs, we will not get an accurate state at all. The only thing that can be done is to overthrow it and start over.
content
This book covers all the content of the operating system in the computer science "Graduate Examination Syllabus" of the unified national graduate entrance examination. This book is divided into 8 chapters, namely basic principles, process principles, thread principles, memory principles, file principles, I/O principles, multi-core principles, and operating system design.
table of Contents
The first article on basic principles: the falsehood is true, the avenue is invisible
- Chapter 1 Introduction to Operating Systems
- Chapter 2 Operating System History
- Chapter 3 Basic Concepts of Operating System
The second part of the principle of the process: in a trance, there are things in it; in a trance, there are things in it
- Chapter 4 Process
- Chapter 5 Process Scheduling
- Chapter 6 Process Communication
The third part of thread principle: the good ones are irrelevant and cannot be opened, and the good ones are cordless and cannot be solved
- Chapter 7 Threads
- Chapter 8 Thread Synchronization
- Chapter 9 Philosophical Principles of Deadlock Response
- Chapter 10 Lock Implementation
The fourth memory principle: 64KB memory space can meet everyone's memory needs
- Chapter 11 Basic Memory Management
- Chapter 12 Page Memory Management
- Chapter 13 Page Replacement Algorithm
- Chapter 14 Segmented Memory Management
The fifth document principle: if there is a lack of success, it will not be used; if it is too high, it will be used endlessly
- Chapter 15 Disk Operations
- Chapter 16 File System
- Chapter 17 File System Implementation
- Chapter 18 File System Performance
The sixth chapter 1/O principle: the good, the teacher of the bad; the bad, the resource of the good
- Chapter 19 Input and Output
Chapter Seven Principles of Multi-core: Good words are not believed, faith words are not beautiful
- Chapter 20 Multi-core Architecture and Memory
- Chapter 21 Process Synchronization and Scheduling in a Multi-core Environment
The eighth chapter of operating system design: learn more about the poor, not if you keep it
- Chapter 22 Philosophical Principles of Operating System Design
Many people find the operating system boring, boring, or even annoying. Some people even say that it doesn't matter if you don't understand the operating system. Haven't many people written programs before learning the operating system? Some people have even written very large and complicated programs. It can be seen that ignorance of operating systems does not prevent us from learning to use computers.
If the reader thinks this way, I advise you to think again. Although you have written a program, do you know how the program runs on the computer? If you don’t know, how can you be sure that your program will always run correctly? How dare you say that the programs you write make the most of the system's capabilities? A person thinks the operating system is useless because he doesn't know how to use it, or he has no intention to use the operating system. To be clear, if you think the operating system is useless, it is because your programming and program development are at a low level. If you master the operating system, your programming level will be significantly improved.
In other words, if the operating system is useful, my answer is "As you will". If you have the will or action to use the operating system, the operating system is useful; if you do not have the will or action, the operating system is useless. Of course, I hope that readers can understand the huge use of operating systems after reading this book. In case, after reading this book, the reader still feels confused or thinks the operating system is useless, the only thing I can say is "As you will". Of course, I hope that this situation is unlikely to happen.
This "Operating System Philosophy" has a total of 427 pages, divided into 8 chapters and 22 chapters. Those who need the full version can get it in the following way.
Network protocol
There are too many knowledge points of network protocol, and I can't remember after learning. Most readers should have taken computer network courses, and it is not difficult to learn, especially this course has no formulas, more like liberal arts. I learned a lot of things and memorized a lot of things, but after finishing the exam, they "returned it to the teacher".
There are a lot of articles about network protocols on the Internet. When I read it, I feel that others are saying very reasonable, and I seem to understand it, but I can’t stand the question, and I will find that the general process is understood, but many details are still not know. There is still a long way to go from being able to understand to being able to truly understand. Every time I feel as if I have learned it, but I still can't get started in actual application. Although many details have been explored, but when I went to apply and debug, I found that there was still no idea. For example, when the created virtual machine cannot access the Internet, there is still no way to start, and many things that I have learned seem to be useless.
I sum up this phenomenon as follows: I understand when I read it, I play the drum when I ask, and I get confused when I use it.
Therefore, this book uses the "interesting talk" method, which can solve the problem from "personal door to giving up". It combines obscure knowledge points with some interesting stories through metaphors, which makes it easier to help readers systematically, Deeply understand the knowledge points and general workflow of network technology. Of course, the examples used as metaphors will be somewhat different from the real knowledge points and workflow, but it does not matter. Our brain should be a cache, not a hard disk, and remember the knowledge system in an easy-to-understand way. And the general process, when the problem is really solved, you can consult more accurate information.
table of Contents
Chapter 1 Overview of Communication Protocol
Chapter 2 From Second to Third Floor
Chapter 3 Important Transport Layer
Chapter 4 Common Application Layer
Chapter 5 Unfamiliar Data Center
Chapter 6 Networks in Cloud Computing
Chapter 7 Networks in Container Technology
Chapter 8 Microservice Related Agreements
Chapter 9 Network Protocols are Just Cross Talk
This "Interesting Network Protocol" has a total of 435 pages. Those who need the full version can get it in the following ways.
In fact, up to this point, the exploration of the online world has just begun. Only the content generated by your own hands and thoughts is the knowledge that really belongs to you! Turn on your computer and start experimenting!
The operating system and network protocol series documents have been sorted out, welcome to learn together!
