You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A vm allocator shall enable to create continuous memory regions by relying on paging. Currently, paging is only used to have a flat memory space, i.e., virtual memory and physical memory is mapped 1-to-1. The vma region may be at a high address region. The page directory is shared among all cores. It is set during booting time and it never touched again.
To check if current allocator returns page-aligned memory when asking for a PAGE_SIZE
- Current allocator does not return page-aligned chunks when asking for a PAGE_SIZE
To add a page allocator that works only on PAGE_SIZE chunks
To build a simple POC to check paging is working as expected
The chunks that are initiated for each must be aligned to PAGE_SIZE
To review how ToroOS allocates pages.
- ToroOS uses an stack to keep free pages. The stack is stored in the page itself. When a free page is required, we
invoke pop_free_page(), then, push_free_page() is used to push a free page on top of the stack.
To add make current kernel heap to work on the page allocator.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
A vm allocator shall enable to create continuous memory regions by relying on paging. Currently, paging is only used to have a flat memory space, i.e., virtual memory and physical memory is mapped 1-to-1. The vma region may be at a high address region. The page directory is shared among all cores. It is set during booting time and it never touched again.
- Current allocator does not return page-aligned chunks when asking for a PAGE_SIZE
- ToroOS uses an stack to keep free pages. The stack is stored in the page itself. When a free page is required, we
invoke
pop_free_page()
, then,push_free_page()
is used to push a free page on top of the stack.The text was updated successfully, but these errors were encountered: