mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-01-16 15:50:19 +01:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
fd7960e191
max_waves is just for shader-db stats for now, but threadsize will replace the various mechanisms used to determine threadsize across the different gen's. Calculating these correctly entails adding a bunch of details about the sizes of various things to ir3. In the future we will use the guts of the max_waves calculation to inform RA decisions as well, which is why the max_waves calculation is broken up into register dependent/independent pieces. Something should be said about the units of reg_size_vec4. These units were chosen for two reasons: 1. As said in the comment, it makes some calculations easier. 2. For a4xx/a5xx, where we don't know as much because we haven't done the same sorts of experiments to probe for the HW configuration, it corresponds more directly to things that are known. The existing code switches to the smaller threadsize when r24.x or higher is used, which translates directly to a reg_size_vec4 of 48. If we chose different units (e.g. multiplying by wave_granularity and/or threadsize_base), then to match the same behavior we'd have to set reg_size_vec4 based on some other parameters that aren't 100% known. If someone comes along and updates them, they might inadvertantly break it. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9498> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| bin | ||
| build-support | ||
| docs | ||
| doxygen | ||
| include | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .travis.yml | ||
| Android.common.mk | ||
| Android.mk | ||
| CleanSpec.mk | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| REVIEWERS | ||
| VERSION | ||
`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.