Now that we have a frame allocator, I think we need to go back to malloc and rethink how it works. At the moment it relies on a linked list structure denoting what the memory nodes are.
{start: x, end: y, free: true/false} -> ...
This worked for a while, but I think now that I have a frame allocator we need a solution with less overhead (i.e. no linked list).
https://github.com/rfmineguy/malloc-impl
Now that we have a frame allocator, I think we need to go back to malloc and rethink how it works. At the moment it relies on a linked list structure denoting what the memory nodes are.
{start: x, end: y, free: true/false} -> ...
This worked for a while, but I think now that I have a frame allocator we need a solution with less overhead (i.e. no linked list).
https://github.com/rfmineguy/malloc-impl