Mesa needs threading like NVidia card drivers. Please add. Thank you!!
Mesa already does have threading support similar to the NVIDIA drivers. Threading is currently enabled via an application whitelist, as it's helpful for certain games, but hurts others. You can see the current whitelist here: https://cgit.freedesktop.org/mesa/mesa/tree/src/util/drirc If you'd like to force threading to be enabled, just set an environment variable before running the application: export mesa_glthread=true If it helps a particular game, feel free to submit a patch adding the binary name to drirc, so we can whitelist it for everyone. The radeonsi driver also makes use of threading to offload a bunch of work. It also has threaded shader compilation. Currently, none of the above work on the Intel i965 driver. If that's the hardware you're interested in, feel free to reopen this.
Could you add it for Cemu with Wine?
Could you optimize it for better performance with Cemu please? Just compare amd on linux vs nvidia.
Cemu uses OpenGLs compatibility profile (requires at least 4.1) which is unsupported in Mesa. Are you running it with overrides? If not it's going to be slow and likely buggy as it will be falling back to less optimal OpenGL code paths.
(In reply to Zacharybinx34 from comment #2) > Could you add it for Cemu with Wine? As noted above, somebody needs first to do extensive enough testing that threading: * doesn't cause (additional) functional problems * it actually improves performance, instead of decreasing it Before it can be enabled by default in Mesa. However, in case of Wine and other "emulators" translating 3D commands for the programs run through them, testing results for one emulated program, such as "Cemu", isn't necessarily valid for another emulated program. Mesa "drirc" mechanism can identify programs (e.g. Wine) only by their binary name, not what they run inside them (e.g. Cemu). I.e. this kind of whitelist should probably be maintained at Wine side, not Mesa.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.