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
Currently we only use max 128MB memory, this memory is mapped from 0 into the KERNEL_BASE and that's good since we can have something like 1:1 mapping and that's how physical2virtual function works.
But for more memory, we need to have a special physical page allocator, that doesn't have the memory virtually mapped, and thus we can't store the free pages as a linked list connected to one another by we can store the metadata about free pages in the heap somewhere since we have that.
The setup can be done as so.
initial physical page allocator setup
virtual memory setup
[implied] heap setup (for us heap just works after virtual memory is initialized)
allocate rest of ram into high physical page allocator
Can use any amount of memory from ram
The text was updated successfully, but these errors were encountered:
Currently we only use max 128MB memory, this memory is mapped from 0 into the
KERNEL_BASE
and that's good since we can have something like 1:1 mapping and that's howphysical2virtual
function works.But for more memory, we need to have a special physical page allocator, that doesn't have the memory virtually mapped, and thus we can't store the free pages as a linked list connected to one another by we can store the metadata about free pages in the heap somewhere since we have that.
The setup can be done as so.
The text was updated successfully, but these errors were encountered: