2 releases

0.1.1 Mar 11, 2024
0.1.0 May 12, 2022

#39 in Memory management

Download history 12157/week @ 2024-01-25 10803/week @ 2024-02-01 16846/week @ 2024-02-08 15686/week @ 2024-02-15 8232/week @ 2024-02-22 7324/week @ 2024-02-29 9213/week @ 2024-03-07 14095/week @ 2024-03-14 8752/week @ 2024-03-21 6855/week @ 2024-03-28 9293/week @ 2024-04-04 4294/week @ 2024-04-11 7917/week @ 2024-04-18 7543/week @ 2024-04-25 6957/week @ 2024-05-02 6011/week @ 2024-05-09

28,906 downloads per month

Apache-2.0 OR BSD-3-Clause

1.5K SLoC


crates.io docs.rs

vm-allocator is a crate designed to provide allocation and release strategies that are needed by the VMM during the lifetime of a virtual machine. Possible resource types that a VMM could allocate using vm-allocator are MMIO addresses, PIO addresses, GSI numbers, device IDs.

This crate exports 2 allocators: one for resources that can be represented as integers, and one for addresses. The reason behind having two separate allocators is the need to add semantic meaning to the address allocator, by specifying configuration parameters such as the alignment that do not make sense in the context of IDs.

The main components of the crate are:

  • IdAllocator which should be used for all resources that can be reduced to an integer type.
  • AddressAllocator which should be used to allocate address ranges in different address spaces. This component is a wrapper over IntervalTree that adds semantics to address ranges. More details about the inner presentation of the address allocator can be found in the Design Document.

ID Allocator


This allocator should be used to allocate resources that can be reduced to an integer type like legacy GSI numbers or KVM memory slot IDs. The characteristics of such a resource are represented by the IdAllocator struct.

The struct that defines the IdAllocator contains the end of the interval that is managed, a field that points at the next available ID and a BTreeSet that is used to store the released IDs. The reason for using a BTreeSet is that the average complexity for deletion and insertion is O(log N), offering a better performance when compared to Vector for example. The entries are sorted, so we will always use the first available ID.

Allocation policy

When allocating a new ID we always try to return the smallest one available. To do that we first search in the BTreeSet for any ID that was released and if we cannot find anything there we return the next ID from the range that was never allocated.

The IdAllocator struct implements methods for allocating and releasing IDs.


Add vm-allocator as a dependency in Cargo.toml

vm-allocator = "*"

Then add extern crate vm-allocator; to the projects crate root. The VMM using this crate should instantiate an IdAllocator object for each resource type they want to manage.


This project is licensed under either of


~20K SLoC