zink: remove driver-based max_fences throttling
there are no more fence objects, so there's no need to do driver-specific clamping on them the mechanism remains intact to handle ETOOMANYSUBMITS Acked-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15904>
This commit is contained in:

committed by
Marge Bot

parent
21fb0a3473
commit
b0cbe3d419
@@ -332,8 +332,8 @@ post_submit(void *data, void *gdata, int thread_index)
|
||||
if (bs->ctx->reset.reset)
|
||||
bs->ctx->reset.reset(bs->ctx->reset.data, PIPE_GUILTY_CONTEXT_RESET);
|
||||
screen->device_lost = true;
|
||||
} else if (bs->ctx->batch_states_count > screen->max_fences) {
|
||||
zink_screen_timeline_wait(screen, bs->fence.batch_id - (screen->max_fences / 2), PIPE_TIMEOUT_INFINITE);
|
||||
} else if (bs->ctx->batch_states_count > 5000) {
|
||||
zink_screen_timeline_wait(screen, bs->fence.batch_id - 2500, PIPE_TIMEOUT_INFINITE);
|
||||
}
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user