Originally posted by cipper
View Post
Announcement
Collapse
No announcement yet.
AMDVLK vs. Mesa RADV Radeon Vulkan Driver Performance On Linux
Collapse
X
-
Originally posted by Quackdoc View Postamdvlk needs to exist anyways for windows, and besides that radv still has various issues (afaik it still doesn't support DRM HDR setting, maybe mistaken though). that may not be super simple to solveLast edited by cipper; 03 June 2023, 04:26 AM.
- Likes 2
Comment
-
- Likes 2
Comment
-
-
-
Originally posted by cipper View Post
you keep reporting the differences between the two drivers, this is not what I'm asking. Is it so hard to understand my question? If you don't have an answer just don't reply.
Nowadays RADV and radeonsi share some code, so that is already an improvement in using developer ressources more efficiently. I don't know what the long term driver strategy is though and if RADV will become their main effort for Windows and Linux somewhen in the future. There were some efforts to build RADV on Windows at least.
- Likes 2
Comment
-
Originally posted by cipper View Post
I guess Windows version has its dedicated devs, that's not relevant. Of course there are differences between the two drivers, but it would be advantageous for amd to collaborate with mesa devs and work to merge amdvlk and radv in a single mesa driver. Especially given the good performance of radv. The question is: what prevents amd to do that?
AMDVLK is essentially the windows vulkan driver - AMD's proprietary shader compiler + the open source LLVM shader compiler backend.
The windows driver and AMDVLK both use a common hardware abstraction layer to talk to the kernel, which is not used at all in mesa.
So maintaining AMDVLK as-is is cheap and low burden for AMD, while supporting RADV directly would mean either supporting two totally separate driver stacks, where any improvements they make won't translate over "automatically" to the other platforms they support - or rearchitecting their whole driver stack on non-linux platforms to use mesa at great cost.
- Likes 3
Comment
-
Originally posted by cipper View Post
I guess Windows version has its dedicated devs, that's not relevant. Of course there are differences between the two drivers, but it would be advantageous for amd to collaborate with mesa devs and work to merge amdvlk and radv in a single mesa driver. Especially given the good performance of radv. The question is: what prevents amd to do that?
Originally posted by airminer View PostSo maintaining AMDVLK as-is is cheap and low burden for AMD, while supporting RADV directly would mean either supporting two totally separate driver stacks, where any improvements they make won't translate over "automatically" to the other platforms they support - or rearchitecting their whole driver stack on non-linux platforms to use mesa at great cost.
- Likes 3
Comment
-
I tested this a while back https://youtu.be/MRKEpmqvYR8
Apart from Cyberpunk, which seems to perform decent on AMDVLK, other games perform terribly, RADV is still king
Comment
Comment