Sebastien Boeuf 709148803e vm-allocator: Fix free range allocation ... This patch fixes the function first_available_range() responsible for finding the first range that could fit the requested size. The algorithm was working, that is allocating ranges from the end of the address space because we created an empty region right at the end. But the problem is, the VMM might request for some specific allocations at fixed address to allocate the RAM for example. In this case, the RAM range could be 0-1GiB, which means with the previous algorithm, the new available range would have been found right after 1GiB. This is not the intended behavior, and that's why the algorithm has been fixed by this patch, making sure to walk down existing ranges starting from the end. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>		2019-07-22 09:51:16 -07:00
..
src	vm-allocator: Fix free range allocation	2019-07-22 09:51:16 -07:00
Cargo.toml	allocator: Add a basic resource allocation crate	2019-05-08 08:55:06 +02:00