This is an important step to prepare a split of the existing implementation APIs into a type-management part and a memory-allocation part; generally speaking, a memory allocator needs to know the allocation size, preferably also for releasing memory. Up to now, this information could be retrieved locally, with a metadata lookup through the hash-ID; now we ensure that the size is always passed alongside through the implementation API. Incidentally, it looks like we might be able to form a common allocation-descriptor, to represent this internal API in a more concise way. Note further that all these changes are considered not relevant for the performance, since work buffers are large and media computation dominates.
11 MiB
11 MiB
| The file is too large to be shown. |