diff options
| author | Nicolai Hähnle <nicolai.haehnle@amd.com> | 2016-09-09 11:49:18 +0200 |
|---|---|---|
| committer | Nicolai Hähnle <nicolai.haehnle@amd.com> | 2016-09-27 16:45:05 +0200 |
| commit | 6d89a4067627fdf568c6c4e3d9a201fd45d5352b (patch) | |
| tree | 0ba77efad5bc9db0bd42a4414d1c194334a5ed3f /src/gallium/drivers/r300 | |
| parent | e703f71ebdf91938c83f47c898f1da058ce0ac32 (diff) | |
| download | external_mesa3d-6d89a4067627fdf568c6c4e3d9a201fd45d5352b.zip external_mesa3d-6d89a4067627fdf568c6c4e3d9a201fd45d5352b.tar.gz external_mesa3d-6d89a4067627fdf568c6c4e3d9a201fd45d5352b.tar.bz2 | |
gallium/radeon: add RADEON_FLAG_HANDLE
When passed to winsys->buffer_create, this flag will indicate that we require
a buffer that maps 1:1 with a kernel buffer handle.
This is currently set for all textures, since textures can potentially be
exported to other processes. This is not a huge loss, since the main purpose
of this patch series is to deal with applications that allocate many small
buffers.
A hypothetical application with tons of tiny textures might still benefit
from not setting this flag, but that's not a use case I'm worried about
just now.
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Diffstat (limited to 'src/gallium/drivers/r300')
| -rw-r--r-- | src/gallium/drivers/r300/r300_texture.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/gallium/drivers/r300/r300_texture.c b/src/gallium/drivers/r300/r300_texture.c index 5f459e4..fbac07a 100644 --- a/src/gallium/drivers/r300/r300_texture.c +++ b/src/gallium/drivers/r300/r300_texture.c @@ -1114,7 +1114,7 @@ r300_texture_create_object(struct r300_screen *rscreen, /* Create the backing buffer if needed. */ if (!tex->buf) { tex->buf = rws->buffer_create(rws, tex->tex.size_in_bytes, 2048, - tex->domain, 0); + tex->domain, RADEON_FLAG_HANDLE); if (!tex->buf) { goto fail; |