A good read-only book, ComputerSystemsAProgrammer 'sperspective

A good read-only book, A ComputerSystemsAProgrammersPerspective-Linux general technology-Linux programming and kernel information. Read the following for details. Recently I read A really good book called Computer Systems A Programmer's Perspective, which breaks down A lot of things and is concise, but incisive. each piece is the essence, after reading it, you will understand a lot of things. Great!

Many things explain the knowledge of computer systems using ansi c and AT&T. Obviously!

Speaking of AT&T assembly, it is really a good thing. If you want to know about the Linux kernel, can't you not use AT&T assembly?

I also need to be proficient in linux written in C language. But at the bottom, isn't AT&T still used for compilation?

Most of the books on assembly outside China are compiled by AT&T, and a few of them are basically compiled by intel. They are classic books. I have also read them. Indeed, the various instruction statements of the assembly language are fully written. However, they are MASM-format assemblies that are commonly used in China.

In fact, I didn't learn compilation much during my undergraduate course, But I basically didn't learn it because I thought it was useless. It was a good thing. I had to pay it back sooner or later, I am crazy about compilation, and I am still fascinated by the results.

I 've learned this for almost half a lifetime. The only thing I don't regret is to study this year. I learned a lot and did a lot of things seriously. I have never regretted it since I graduated from elementary school to a bachelor's degree. I regret it. I learned why I didn't follow my feelings and why I didn't do my best.

(The company's network is speechless. The download speed is 1-2 Mbit/s, but sometimes a picture cannot be refreshed !)

After planning, you have time to look at distributed computing.

I have a classmate who said that reading the linux kernel source code is useless. At that time, I joined him. In fact, it is very important, unless you did not understand the linux kernel code and many things, it's not what the linux system does, but what the cpu does, but what we think is that everything we don't see and what we can't control is what the operating system is doing, the operating system only initializes many things according to CPU requirements (the majority of hardware), and many user requirements. The operating system simply converts the data, commands, and addresses to the CPU, (Of course, I am also a little excited, just like the feeling of CPU supremacy), I just want to express that a lot of things are not actually done by the operating system, but simply put forward requests to the CPU or hardware. We need to face up to the CPU and operating system! If something goes wrong, we need to know who is doing it. We can fix it, rather than simply accept it!