✳flâneur — a map of the web's best reading

The thread struct | Pintos Documentation

cs162.org · 839 words · saved by 1 readers

Each thread struct represents either a pure kernel thread (i.e. a thread that only runs kernel code) or a thread in a user process. In each of the 3 projects, you will have to add your own members to the thread struct. You may also need to change or delete the definitions of existing members. Every thread struct occupies the beginning of its own 4 KiB page of memory. The rest of the page is used for the thread’s stack, which grows downward from the end of the page. It looks like this: This layout has two consequences. First, struct thread must not be allowed to grow too big. If it does, then there will not be enough room for the kernel stack. The base struct thread is only a few bytes in size. It probably should stay well under 1 kB. Second, kernel stacks must not be allowed to grow too large. If a stack overflows, it will corrupt the thread state. Thus, kernel functions should not allocate large structures or arrays as non-static local variables. Use dynamic allocation with malloc() o

The thread struct | Pintos Documentation Skip to main content Menu Expand (external link) Document Search Copy Copied Pintos Documentation The thread struct Each thread struct represents either a pure kernel thread (i.e. a thread that only runs kernel code) or a thread in a user process. In each of the 3 projects, you will have to add your own members to the thread struct. You may also need to change or delete the definitions of existing members. Every thread struct occupies the beginning of its own 4 KiB page of memory. The rest of the page is used for the thread’s stack, which grows downward

Explore this link on the map →

related reading