anv: Use an anv_state for the next binding table
authorJason Ekstrand <jason@jlekstrand.net>
Thu, 7 Nov 2019 20:02:09 +0000 (14:02 -0600)
committerJason Ekstrand <jason@jlekstrand.net>
Mon, 18 Nov 2019 18:35:14 +0000 (18:35 +0000)
commitbc9d7836bc6a448d0328f090b8d538411f8aa1a0
treec555ba80360a2f046541dce0fd7fa056fe272ea8
parent98dc179c1e094ab42346b23fe046ebb719b66ed4
anv: Use an anv_state for the next binding table

This is a bit more natural because we're already getting an anv_state
most places in the pipeline.  The important part here, however, is that
we're no longer calling anv_block_pool_map on every alloc_binding_table
call.  While it's probably pretty cheap, it is potentially a linear walk
over the list of BOs and it was showing up in profiles.

Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
src/intel/vulkan/anv_batch_chain.c
src/intel/vulkan/anv_private.h