mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-08 11:18:08 +02:00
read-only mirror of https://gitlab.freedesktop.org/mesa/mesa
93659e4ed3
When calling glWaitSync (fence_server_sync), we added dependencies in all batches (render and compute) on existing work. Even if applications don't use compute at all, they theoretically could, so we record that the compute batch depends on the render batch. But if the application truly doesn't use compute, or rarely uses it, we ended up recording dependencies on _all_ previous render batches, racking up a massive list of syncobjs. Not only is this pointless, it also meant that we never allowed the kernel to free the underlying i915_request objects. There are a number of solutions to this problem, but for now, we take a simple one: when recording a new syncobj dependency, we walk the list and see if any of them have already passed. If so, that dependency has been fulfilled. We no longer need to track it, and can simply drop it from the list, unreferencing the syncobj. Android's SurfaceFlinger in particular was hitting this issue, as it uses glWaitSync, doesn't typically use compute shaders, and runs for long durations. Thanks to Yang A Shi <yang.a.shi@intel.com> and Kefei Yao <kefei.yao@intel.com> for their excellent work in tracking down this issue! Fixes: |
||
|---|---|---|
| .appveyor | ||
| .gitlab/issue_templates | ||
| .gitlab-ci | ||
| bin | ||
| build-support | ||
| docs | ||
| doxygen | ||
| include | ||
| scons | ||
| src | ||
| subprojects | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .pick_status.json | ||
| .travis.yml | ||
| Android.common.mk | ||
| Android.mk | ||
| appveyor.yml | ||
| CleanSpec.mk | ||
| common.py | ||
| meson.build | ||
| meson_options.txt | ||
| README.rst | ||
| REVIEWERS | ||
| SConstruct | ||
| 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.