ce2e2296ab
With all the preparation in place to handle suballocated BOs at submission and export, we can now wire up the actual suballocator. We use Gallium's pb_slab infrastructure for this, which is already used for this purpose in the amdgpu winsys and now zink as well. Unlike those drivers, we don't use pb_buffer (it doesn't do much) nor pb_cache (we already have a buffer cache). Just pb_slab for now. We can now suballocate BOs at power-of-two (or 3/4 power-of-two) granularity, between 256B and 2MB. Beyond that, we use actual GEM objects as before. This should save us some memory on current GPUs where we previously had a minimum allocation granularity of 4K (page size), but should save us a /ton/ of memory on future GPUs where the minimum page size is 64K. Fewer actual GEM objects should also mean shorter exec_object2 lists passed to the kernel, which could reduce CPU overhead a bit. Using large allocations where the underlying GEM objects correspond with the PTE fragment size may also allow the kernel to use a more efficient page table layout, improving memory access times. This cuts nearly half of the memory usage in a Unity3D demo on a GPU that uses 64K pages. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/4722 Acked-by: Paulo Zanoni <paulo.r.zanoni@intel.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12623> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| android | ||
| bin | ||
| build-support | ||
| docs | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| README.rst | ||
| REVIEWERS | ||
| VERSION | ||
| meson.build | ||
| meson_options.txt | ||
README.rst
`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 `OFTC's #dri-devel <irc://irc.oftc.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.