1
0
mirror of https://github.com/doitsujin/dxvk.git synced 2024-11-30 04:24:11 +01:00

[dxvk] Don't put large resources into their own memory allocations

This approach currently has two issues:
- We might fail to allocate the resource on the desired memory type
  even if there is a chunk available that it would tif in
- With 128MB chunks, this no longer seems to be beneficial anyway
This commit is contained in:
Philip Rebohle 2019-07-16 09:24:55 +02:00
parent ad8fdcac07
commit 18aada29ef
No known key found for this signature in database
GPG Key ID: C8CC613427A31C99

View File

@ -284,7 +284,7 @@ namespace dxvk {
DxvkMemory memory;
if ((size >= type->heap->chunkSize / 4) || dedAllocInfo) {
if (size >= type->heap->chunkSize || dedAllocInfo) {
DxvkDeviceMemory devMem = this->tryAllocDeviceMemory(
type, flags, size, priority, dedAllocInfo);