vk/allocator: Use memory pools rather than (MALLOC|FREE)LIKE
authorJason Ekstrand <jason.ekstrand@intel.com>
Fri, 31 Jul 2015 17:36:51 +0000 (10:36 -0700)
committerJason Ekstrand <jason.ekstrand@intel.com>
Fri, 31 Jul 2015 17:38:28 +0000 (10:38 -0700)
commite65953146c817e8bb98dd91788ad4d46775d40b8
treecf29e654df5415ac26492c7b350e149936142fdd
parent1920ef9675b5ebdab2050b1f37c6cfdd6d9c6f69
vk/allocator: Use memory pools rather than (MALLOC|FREE)LIKE

We have pools, so we should be using them.  Also, I think this will help
keep valgrind from getting confused when we have to end up fighting with
system allocations such as those from malloc/free and mmap/munmap.
src/vulkan/anv_allocator.c