#3582 assigned task

Remove dedicated support for boundary constraint in heap allocator

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 6.1
Component: score Version: 5
Severity: normal Keywords:
Cc: Blocked By:


Some time ago a dedicated support for a boundary constraint was added to the first fit heap allocator. The use case for this is the libbsd (new network stack) which needs this for the bus space allocator:


It turned out that this feature is rarely used. It makes the first fit heap allocator implementation considerably more complex. It is also not a standard allocator feature which makes it more difficult to replace the first fit heap allocator with something else, e.g. TLSF.

The boundary constraint can be also satisfied by an allocator which supports only the alignment constraint via:

if (boundary > alignment) {
	assert(alignment == 0 || boundary % alignment == 0);
	alignment = boundary;

Change History (1)

comment:1 Changed on Dec 19, 2019 at 8:07:34 AM by Sebastian Huber

Milestone: 5.16.1
Note: See TracTickets for help on using tickets.