Originally posted by Almindor
View Post
Announcement
Collapse
No announcement yet.
A Closer Look At The AMDVLK vs. RADV vs. AMDGPU-PRO Vulkan Performance
Collapse
X
-
Michael Larabel
https://www.michaellarabel.com/
- Likes 2
-
Originally posted by Michael View Post
When AMD has to continue supporting "AMDVLK" regardless due to the Windows Vulkan support, unfortunately, it's not a trivial route with RADV already working out so well but not easily portable to Windows nor AMD's proprietary shader compiler, etc.
- Likes 2
Comment
-
Originally posted by Duve View Post
Honestly I would think that targeting RADV makes more sense, it's propagates around distributions rather well considering where it is it at in concerns to maturity. If Linux is a target, and you want a wide swath of users, then it hard to argue against it at this point... I would think.
The Pro-RADV-argument has come up so many times now that I can't help but to think that it is some kind of stubborn clining to the established open source projects like Mesa. Even though AMD has now open sourced their driver after a yearlong effort, people don't seem to find it "open source" or "community driven" enough. Weird.
Finally, chances are that game devs will target AMDVLK since they will have to optimize for Windows anyway.
Comment
-
Originally posted by GruenSein View Post
That is a very Linux-centric point of view. Remember: The majority of the GPU-market is on Windows. This means, whatever driver they use there has to be supported. RADV is not an option on windows. Maintaining a second, totally different driver on Linux is a horrible waste of developer resources. Every new GPU would have to be supported on both drivers. Optimizations would have to be done on both drivers. Some might not even translate across platforms.
The Pro-RADV-argument has come up so many times now that I can't help but to think that it is some kind of stubborn clining to the established open source projects like Mesa. Even though AMD has now open sourced their driver after a yearlong effort, people don't seem to find it "open source" or "community driven" enough. Weird.
Finally, chances are that game devs will target AMDVLK since they will have to optimize for Windows anyway.
Dave.
- Likes 4
Comment
-
Originally posted by starshipeleven View PostIf AMDVLK is supposed to stay relatively in sync with the windows version, then RADV will probably win the race.
Or it can go the other way around: AMDVLK picks up improvements from RADV and vice-versa, and the Windows version gets synced to benefit from AMDVLK.
- Likes 1
Comment
-
airlied
Basically it should be possible to package AMDVLK relatively easy. It is always good to have got a 2nd choice - the question is just how to select the default Vulkan driver.
Btw. is OpenCL for Polaris 12/Vega already fully open source and packaged for Debian - had problems installing 17.50 with in compute mode with Debian Stretch. With a mesa+llvm backport at least OpenGL+Vulkan works.
Comment
Comment