5 commits

Author	SHA1	Message	Date
Bill Currie	1fd02322f4	[util] Clean up some minor issues in cmem ... I forgot to remove the noinline attribute and do a check with optimization (to catch the "pure" recommendation).	2021-01-01 22:29:31 +09:00
Bill Currie	9090c53519	[util] Add failing sub-line allocator tests ... I think the sub-line allocator falling over is the final source of qfvis's leaks. It certainly causes a mess of the sub-lines. But having some tests to get working sure beats scratching my head over qfvis :)	2020-12-30 18:20:11 +09:00
Bill Currie	d12abc5132	[util] Relink grown free line block ... This fixes one source of memory leaks, but it seems some are still lurking as qfvis still leaks like a sieve.	2020-12-30 18:20:11 +09:00
Bill Currie	4039075f41	[util] Use a linked list of free cache lines ... The idea is to not search through blocks for an available allocation. While the goal was to speed up allocation of cache lines of varying cluster sizes, it's not enough due to fragmentation.	2020-12-30 18:20:11 +09:00
Bill Currie	af814ff9a8	[util] Add a cache-line aligned memory allocator ... This was inspired by Hoard: A Scalable Memory Allocator for Multithreaded Applications Emery D. Berger, Kathryn S. McKinley, Robert D. Blumofe, Paul R. Wilson, It's not anywhere near the same implementation, but it did take a few basic concepts. The idea is twofold: 1) A pool of memory from which blocks can be allocated and then freed en-mass and is fairly efficient for small (4-16 byte) blocks 2) Tread safety for use with the Vulkan renderer (and any other multi-threaded tasks). However, based on the Hoard paper, small allocations are cache-line aligned. On top of that, larger allocations are page aligned. I suspect it would help qfvis somewhat if I ever get around to tweaking qfvis to use cmem.	2020-12-21 14:14:29 +09:00