| 1 | RADV VS. AMDVLK VS. RADEON SOFTWARE VULKAN DRIVER PERFORMANCE - \r |
| 2 | OCTOBER 2018 LINUX GAMING \r |
| 3 | \r |
| 4 | [linux_gaming] 2018-10-09_15-00\r |
| 5 | \r |
| 6 | o Reference: 2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad\r |
| 7 | o News link: https://www.reddit.com/r/linux_gaming/comments/9lewod/radv_vs_amdvlk_vs_radeon_software_vulkan_driver/\r |
| 8 | o Source link: https://www.phoronix.com/scan.php?page=article&item=amdvlk-radv-okt18&num=1\r |
| 9 | \r |
| 10 | \r |
| 11 | The fact that there are two drivers is the biggest\r |
| 12 | headscratcher from AMD really since they started really doing\r |
| 13 | a good job. I can't see why they are fragmenting that one\r |
| 14 | specific thing rather than just slowly merging it into RADV.\r |
| 15 | \r |
| 16 | \r |
| 17 | ** FlukyS\r |
| 18 | The fact that there are two drivers is the biggest headscratcher\r |
| 19 | from AMD really since they started really doing a good job. I\r |
| 20 | can't see why they are fragmenting that one specific thing\r |
| 21 | rather than just slowly merging it into RADV.\r |
| 22 | \r |
| 23 | ** PolygonKiwii\r |
| 24 | Because radv isn't their driver and amdvlk shares its code\r |
| 25 | with the windows driver.\r |
| 26 | But it's not that bad, as the biggest performance gains will\r |
| 27 | likely come from optimizing llvm, which both drivers make use\r |
| 28 | of*.\r |
| 29 | Also it's not a problem to install two Vulkan drivers side by\r |
| 30 | side so users could always do that if they really need both.\r |
| 31 | * except for the pro stack, which uses a proprietary compiler\r |
| 32 | shared with windows. I think their plan was to improve llvm\r |
| 33 | and replace the proprietary compiler when llvm caught up in\r |
| 34 | performance, but don't quote me on that\r |
| 35 | \r |
| 36 | \r |
| 37 | \r |