Exercises


1:

Why can't processes executed from a common executable or program not share the data segments of memory?

2:

What would the stack of the following function look like after three iterations?

 foo(){   int a;   foo() } 

If it continues, what problem is this going to run into?

3:

Fill in the values for the vm_area_struct descriptors that correspond to the memory map shown in Figure 4.11.

4:

What is the relationship between pages and slabs?

5:

A 32-bit system with Linux loaded does not use the Page Middle Directory. That is, it effectively has a two-level page table. The first 10 bits of the virtual address correspond to the offset within the Page Global Directory (PGD). The second 10 bits correspond to an offset into the Page Table (PTE). The remaining 12 bits correspond to the page offset.

What is the page size in this Linux system? How many pages can a task access? How much memory?

6:

What is the relationship between a memory zone and a page?

7:

At the hardware level, how does "real" addressing differ from "virtual" addressing?




The Linux Kernel Primer. A Top-Down Approach for x86 and PowerPC Architectures
The Linux Kernel Primer. A Top-Down Approach for x86 and PowerPC Architectures
ISBN: 131181637
EAN: N/A
Year: 2005
Pages: 134

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net