diff options
author | Marek Olšák <[email protected]> | 2017-10-26 03:17:29 +0200 |
---|---|---|
committer | Marek Olšák <[email protected]> | 2017-11-06 19:09:12 +0100 |
commit | 71f5fe36b7f4f092398d27a130ef18b7e0913889 (patch) | |
tree | f9ab4e6ee98b5fd277e5d775108376c26aae373a /src/gallium/auxiliary/util/u_upload_mgr.c | |
parent | 3f58988b81965fc70fe8770b4d8912cf12f0a6f1 (diff) |
gallium/u_vbuf: use signed vertex buffers offsets for optimal uploads
Uploaded data must start at (stride * start), because we can't modify
start in all cases. If it's the first allocation, it's also the amount
of memory wasted. If the starting offset is larger than the size of
the upload buffer, the buffer is re-created, used for 1 upload, and then
thrown away. If the upload is small, most of the buffer space is unused
and wasted. Keep doing that and the OOM killer comes. It's actually
pretty quick.
With signed VB offsets, we can set min_out_offset = 0
in u_upload_alloc/u_upload_data.
This fixes OOM situations with SPECviewperf.
Diffstat (limited to 'src/gallium/auxiliary/util/u_upload_mgr.c')
0 files changed, 0 insertions, 0 deletions