doc: explain the default_page_table
This commit is contained in:
parent
6533334824
commit
a72c3ca195
BIN
documentation/assets/memory/heap_map.webp
Normal file
BIN
documentation/assets/memory/heap_map.webp
Normal file
Binary file not shown.
After Width: | Height: | Size: 8.9 KiB |
@ -2,4 +2,9 @@
|
|||||||
|
|
||||||
## Pagination
|
## Pagination
|
||||||
|
|
||||||
To activate pagination you must put the physic [pd](./memory/page_directory.md) address in the cr3 register and 0x80000000 in the cr0 register. Now the [MMU](./memory/mmu.md) will translate your address
|
To activate pagination you must put the physic [pd](./memory/page_directory.md) address in the cr3 register and 0x80000000 in the cr0 register. Now the [MMU](./memory/mmu.md) will translate your address
|
||||||
|
|
||||||
|
### Our setup
|
||||||
|
|
||||||
|
Cause create all [pt](./memory/page_table.md) will cost 3MB (768 * 1024 * 4, 768: cause is our heap limite, 1024: cause each pt contains 1024 entry and 4: cause size of pte is 4byte) we decided to create it on the heap and dynamically. So the first pt of the pd (pd[0]) will contain a default_page_table (or heap_pt). Each page create by each the heap_pt will be a pt added to the pd.
|
||||||
|
![](./assets/memory/heap_map.webp)
|
||||||
|
Loading…
Reference in New Issue
Block a user