MIT6.S081 Summary

In a daze, I went through MIT6.S081, briefly talk about my feelings, and review it

Process

To be honest, the progress is quite slow. I originally planned to give up the Lab at the end of the semester, but it has been delayed until now

It took me more than a month to read OSTEP at the beginning of school, and I know what the operating system is about.
Then I watched a few NJU JYY OS classes and reshaped the world view of computers.Ready to start flashing the operating system Lab of MIT6.s081

The rhythm was interrupted frantically later. About two months after the start of the school, there was no complete free time at the end of the semester. Exams + group assignments in several courses + a bunch of course design

This led to reading some materials last week, and then during the week when I was busy with school, I couldn't write half of the lab writing on the weekend, and then I continued to work on school the next week, and when I came back to write the lab on the weekend, I forgot what I wrote.what the hell.

At the end of the progress, I basically wrote half of the Lab, especially the COW Lab that made me feel dizzy. I read the original code of xv6 for a few days, then wrote the code that the Lab wanted for a few days, and then adjusted it again.I have written the code for several days, and finally it is better to start it all over again

Then I came back during the summer vacation to make up the framework project of the server, while making up this operating system experiment and intermittently messing with it for nearly a month before it was almost completed

Major mistakes

Incorrect view of data

Official information

• xv6 Manual
• RISC-V related materials
• Courseware PPT
• The video of the lecture (I watched it directly with the big guy's translation)

At first, I just slammed the English version of the xv6 manual, and then I was very confused, because this thing is basically the xv6 code parsing manual, not the operating system textbook.Only later did I feel that the correct way should be

1. Class lectures
2. Courseware PPT
3. xv6 Manual
4. xv6 code
5. Lab

Organizing notes the wrong way

It was only after the course was finished that I realized that what we call good books and good lessons are ultimately output through ourselves (for example, we have to tell others during an interview).So how you organize your notes depends on how you want to output what you learn, not excerpts.So I simply deleted the original notes and reorganized them in a problem-oriented way

• Collect questions from courseware, lecture notes, labs
• Then look for answers from various sources

Harvest

• Established a personal computer world view, jyy I drop Superman
• I feel a little bit of system design: requirements->refinement text description->easy-to-understand schematic diagram->data structure design->implementation of data structure operations
• Understand some concepts and technical means of the operating system from the code level
• I did a few things that sounded relatively nb (although it may seem quite stretched to the layman) to enrich the resume and enhance the competitiveness
• A major mistake is also a major gain in a way
  
• Some engineering ways of thinking have made a little progress

TODO

• Continue to organize relevant notes and documents until you can clearly describe what you have learned and what you have done to others
• I haven't written code for a long time to make up for the foundation. The pure C language pointer streaking made me realize the weakness of the basic skills of the code
• The main part of the OS course has come to an end for the time being. Next semester, I'm going to learn CS144 Hand Rub TCP, let's start!