5 commits

Author	SHA1	Message	Date
Bill Currie	72280186bf	[qfvis] Use cmem for memory management ... While the main bulk of the improvement (36s down from 42s for gmsp3v2.bsp on my i7-6850K) comes from using a high-tide allocator for the windings (which necessitated using a fixed size), it is ever so slightly faster than using malloc as the back-end.	2021-03-27 20:30:35 +09:00
Bill Currie	60348ab458	[headers] Fix some inconsistent include guards	2021-03-03 16:41:05 +09:00
Bill Currie	73544f0790	[util] Split cmem's free cache-line over size bins ... They're binned by powers of two (with in between sizes going to the smaller bin should I make cache-line allocations NPOT (which I think might be worthwhile). However, there seems to still be a bug somewhere causing a nasty leak as now my hacked qfvis consumes 40G in less than a minute.	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