summaryrefslogtreecommitdiffstats
path: root/src/video_core/renderer_vulkan/vk_memory_manager.cpp (follow)
Commit message (Collapse)AuthorAgeFilesLines
* vulkan_common: Move allocator to the common directoryReinUsesLisp2021-01-151-227/+0
| | | | Allow using the abstraction from the OpenGL backend.
* renderer_vulkan: Rename Vulkan memory manager to memory allocatorReinUsesLisp2021-01-151-7/+7
| | | | | "Memory manager" collides with the guest GPU memory manager, and a memory allocator sounds closer to what the abstraction aims to be.
* vk_memory_manager: Improve memory manager and its APIReinUsesLisp2021-01-151-120/+117
| | | | | | | | | Fix a bug where the memory allocator could leave gaps between commits. To fix this the allocation algorithm was reworked, although it's still short in number of lines of code. Rework the allocation API to self-contained movable objects instead of naively using an unique_ptr to do the job for us. Remove the VK prefix.
* renderer_vulkan: Move device abstraction to vulkan_commonReinUsesLisp2021-01-041-1/+1
|
* renderer_vulkan: Rename VKDevice to DeviceReinUsesLisp2021-01-031-4/+4
| | | | | | | The "VK" prefix predates the "Vulkan" namespace. It was carried around the codebase for consistency. "VKDevice" currently is a bad alias with "VkDevice" (only an upcase character of difference) that can cause confusion. Rename all instances of it.
* vulkan_common: Rename renderer_vulkan/wrapper.h to vulkan_common/vulkan_wrapper.hReinUsesLisp2020-12-311-1/+1
| | | | Allows sharing Vulkan wrapper code between different rendering backends.
* video_core: Rewrite the texture cacheReinUsesLisp2020-12-301-1/+1
| | | | | | | | | | | | | | The current texture cache has several points that hurt maintainability and performance. It's easy to break unrelated parts of the cache when doing minor changes. The cache can easily forget valuable information about the cached textures by CPU writes or simply by its normal usage.The current texture cache has several points that hurt maintainability and performance. It's easy to break unrelated parts of the cache when doing minor changes. The cache can easily forget valuable information about the cached textures by CPU writes or simply by its normal usage. This commit aims to address those issues.
* video_core: Resolve more variable shadowing scenarios pt.2Lioncash2020-12-051-9/+9
| | | | | | | Migrates the video core code closer to enabling variable shadowing warnings as errors. This primarily sorts out shadowing occurrences within the Vulkan code.
* vk_memory_manager: Make use of designated initializers where applicableLioncash2020-07-171-7/+6
|
* vk_memory_manager: Remove unified memory model flagReinUsesLisp2020-04-221-12/+1
| | | | | | | | All drivers (even Intel) seem to have a device local memory type that is not host visible. Remove this flag so all devices follow the same path. This fixes a crash when trying to map to host device local memory on integrated devices.
* renderer_vulkan: Drop Vulkan-HppReinUsesLisp2020-04-111-60/+44
|
* vk_memory_manager: Misc changesReinUsesLisp2020-01-061-76/+82
| | | | | | | | | | | | | | | | | | | * Allocate memory in discrete exponentially increasing chunks until the 128 MiB threshold. Allocations larger thant that increase linearly by 256 MiB (depending on the required size). This allows to use small allocations for small resources. * Move memory maps to a RAII abstraction. To optimize for debugging tools (like RenderDoc) users will map/unmap on usage. If this ever becomes a noticeable overhead (from my profiling it doesn't) we can transparently move to persistent memory maps without harming the API, getting optimal performance for both gameplay and debugging. * Improve messages on exceptional situations. * Fix typos "requeriments" -> "requirements". * Small style changes.
* vk_memory_manager: Reorder constructor initializer list in terms of member declaration orderLioncash2019-02-271-1/+1
| | | | | Reorders members in the order that they would actually be initialized in. Silences a -Wreorder warning.
* vk_memory_manager: Fixup commit interval allocationReinUsesLisp2019-02-241-2/+1
| | | | | VKMemoryCommitImpl was using as the end of its interval "begin + end". That ended up wasting memory.
* vk_memory_manager: Implement memory managerReinUsesLisp2019-02-191-0/+253
A memory manager object handles the memory allocations for a device. It allocates chunks of Vulkan memory objects and then suballocates.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-12 00:55:01 +0200