Alejandro Piñeiro
2adea940f1
Heavily based on the already existing for the v3d OpenGL driver, but without references, and with some extra OOM checks (Vulkan CTS has several OOM tests). With this commit v3dv_bo_alloc and v3dv_bo_free became frontends to the bo_cache. The former tries to get a BO from the cache if possible, and the latter stores the BO on the cache if possible. The former also adds a new parameter to point if the BO to allocate is private. As v3d we are only caching private BOs, those created by the driver for internal use (like CLs, tile_alloc, etc). They are the ones with the highest change of being reused (for example, CL BOs are always 4KB, so they can always be reused). User-created BOs can have any size, including some very large ones for buffers and images, which makes them far less likely to be reused and would add a lot of memory pressure if we decided to cache them. In any case, in practice, we found that we could get a performance improvement by caching also user-created BOs, but that would need more care and an analysis to decide which ones makes sense. Would also require to change how the cached BOs are stored by size. Right now there are an array of list_head, that doesn't work well with big BOs. If done, that would be handled on a separate commit. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6766>
`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library ====================================================== Source ------ This repository lives at https://gitlab.freedesktop.org/mesa/mesa. Other repositories are likely forks, and code found there is not supported. Build & install --------------- You can find more information in our documentation (`docs/install.rst <https://mesa3d.org/install.html>`_), but the recommended way is to use Meson (`docs/meson.rst <https://mesa3d.org/meson.html>`_): .. code-block:: sh $ mkdir build $ cd build $ meson .. $ sudo ninja install Support ------- Many Mesa devs hang on IRC; if you're not sure which channel is appropriate, you should ask your question on `Freenode's #dri-devel <irc://chat.freenode.net#dri-devel>`_, someone will redirect you if necessary. Remember that not everyone is in the same timezone as you, so it might take a while before someone qualified sees your question. To figure out who you're talking to, or which nick to ping for your question, check out `Who's Who on IRC <https://dri.freedesktop.org/wiki/WhosWho/>`_. The next best option is to ask your question in an email to the mailing lists: `mesa-dev\@lists.freedesktop.org <https://lists.freedesktop.org/mailman/listinfo/mesa-dev>`_ Bug reports ----------- If you think something isn't working properly, please file a bug report (`docs/bugs.rst <https://mesa3d.org/bugs.html>`_). Contributing ------------ Contributions are welcome, and step-by-step instructions can be found in our documentation (`docs/submittingpatches.rst <https://mesa3d.org/submittingpatches.html>`_). Note that Mesa uses gitlab for patches submission, review and discussions.