AlexIndustrial/mesa
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nvc0: tie buffer memory release to the buffer fence

Browse Source 
... instead of the next fence to be emitted. This way we have a
chance to reclaim the storage earlier.
This commit is contained in:
Christoph Bumiller
2011-01-05 01:41:49 +01:00
parent 96d8a54716
commit bd301dfc12
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/gallium/drivers/nvc0/nvc0_buffer.c
+7 -4
View File
@@ -51,8 +51,12 @@ nvc0_buffer_allocate(struct nvc0_screen *screen, struct nvc0_resource *buf,
static INLINE void
release_allocation(struct nvc0_mm_allocation **mm, struct nvc0_fence *fence)
{
(*mm)->next = fence->buffers;
fence->buffers = (*mm);
if (fence && fence->state != NVC0_FENCE_STATE_SIGNALLED) {
(*mm)->next = fence->buffers;
fence->buffers = (*mm);
} else {
nvc0_mm_free(*mm);
}
(*mm) = NULL;
}
@@ -60,13 +64,12 @@ static void
nvc0_buffer_destroy(struct pipe_screen *pscreen,
struct pipe_resource *presource)
{
struct nvc0_screen *screen = nvc0_screen(pscreen);
struct nvc0_resource *res = nvc0_resource(presource);
nouveau_bo_ref(NULL, &res->bo);
if (res->mm)
release_allocation(&res->mm, screen->fence.current);
release_allocation(&res->mm, res->fence);
if (res->data && !(res->status & NVC0_BUFFER_STATUS_USER_MEMORY))
FREE(res->data);