939bc0c588
Reconfiguring the URB partitioning is likely to cause shader stalls, as the dividing line between each stage's section of memory is moving. (Technically, 3DSTATE_URB_* are pipelined commands, but that mostly means that the command streamer doesn't need to stall.) So it should be beneficial to update the URB configuration less often. If the previous URB configuration already has enough space for our current shader's needs, we can just continue using it, assuming we are able to allocate the maximum number of URB entries per stage. However, if we ran out of URB space and had to limit the number of URB entrties for a stage, and the per-entry size is larger than we need, we should reconfigure it to try and improve concurrency. So, we begin tracking the last URB configuration in the context, and compare against that when updating shader variants. Cuts 36% of the URB reconfigurations (excluding BLORP) from a Shadow of Mordor trace, and 46% from a GFXBench Manhattan 3.0 trace. One nice thing is that this removes the need to look at the old prog_data when updating shaders, which should make it possible to unbind shader variants without causing spurious URB updates. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8721> |
||
|---|---|---|
| .appveyor | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| bin | ||
| build-support | ||
| docs | ||
| doxygen | ||
| include | ||
| scons | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| Android.common.mk | ||
| Android.mk | ||
| CleanSpec.mk | ||
| README.rst | ||
| REVIEWERS | ||
| SConstruct | ||
| VERSION | ||
| appveyor.yml | ||
| common.py | ||
| 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 `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.