--- /dev/null
+ RADV VS. AMDVLK VS. RADEON SOFTWARE VULKAN DRIVER PERFORMANCE - \r
+ OCTOBER 2018 LINUX GAMING \r
+\r
+ [linux_gaming] 2018-10-09_15-00\r
+\r
+ o Reference: 2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad\r
+ o News link: https://www.reddit.com/r/linux_gaming/comments/9lewod/radv_vs_amdvlk_vs_radeon_software_vulkan_driver/\r
+ o Source link: https://www.phoronix.com/scan.php?page=article&item=amdvlk-radv-okt18&num=1\r
+\r
+\r
+ The fact that there are two drivers is the biggest\r
+ headscratcher from AMD really since they started really doing\r
+ a good job. I can't see why they are fragmenting that one\r
+ specific thing rather than just slowly merging it into RADV.\r
+\r
+\r
+ ** FlukyS\r
+ The fact that there are two drivers is the biggest headscratcher\r
+ from AMD really since they started really doing a good job. I\r
+ can't see why they are fragmenting that one specific thing\r
+ rather than just slowly merging it into RADV.\r
+\r
+ ** PolygonKiwii\r
+ Because radv isn't their driver and amdvlk shares its code\r
+ with the windows driver.\r
+ But it's not that bad, as the biggest performance gains will\r
+ likely come from optimizing llvm, which both drivers make use\r
+ of*.\r
+ Also it's not a problem to install two Vulkan drivers side by\r
+ side so users could always do that if they really need both.\r
+ * except for the pro stack, which uses a proprietary compiler\r
+ shared with windows. I think their plan was to improve llvm\r
+ and replace the proprietary compiler when llvm caught up in\r
+ performance, but don't quote me on that\r
+\r
+\r
+\r
git://git.nikiroo.be / gofetch.git / blobdiff