--- /dev/null
+<!DOCTYPE html>
+<html>
+<head>
+ <meta http-equiv='content-type' content='text/html; charset=utf-8'>
+ <meta name='viewport' content='width=device-width, initial-scale=1.0'>
+ <style type='text/css'>
+ body { margin: 1em 15%; }
+ </style>
+</head>
+<body>
+<div class='story'>
+ <h2>RADV vs. AMDVLK vs. Radeon Software Vulkan Driver Performance - October 2018 Linux Gaming</h2>
+ <div class='details'>([linux_gaming] 2018-10-09_15-00)</div>
+ <br/>
+ <ul>
+ <li>Reference: <a href=''>2018-10-09_15-00_RADV_vs__AMDVLK_vs__Rad</a></li>
+ <li>News link: <a href='https://www.reddit.com/r/linux_gaming/comments/9lewod/radv_vs_amdvlk_vs_radeon_software_vulkan_driver/'>https://www.reddit.com/r/linux_gaming/comments/9lewod/radv_vs_amdvlk_vs_radeon_software_vulkan_driver/</a></li>
+ <li>Source link: <a href='https://www.phoronix.com/scan.php?page=article&item=amdvlk-radv-okt18&num=1'>https://www.phoronix.com/scan.php?page=article&item=amdvlk-radv-okt18&num=1</a></li>
+ </ul>
+ <br/>
+ <div class='content' style='text-align: justify'>
+ The fact that there are two drivers is the biggest headscratcher from AMD really since they started really doing a good job. I can't see why they are fragmenting that one specific thing rather than just slowly merging it into RADV.
+ </div>
+<hr/>
+ <div class='comment' style='display: block; margin-left: 80px'>
+ <h3>FlukyS</h3>
+ <div class='by' style='font-style: italic;'></div>
+ <div class='comment_content'><p>The fact that there are two drivers is the biggest headscratcher from AMD really since they started really doing a good job. I can't see why they are fragmenting that one specific thing rather than just slowly merging it into RADV.</p></div>
+ <div class='comment' style='display: block; margin-left: 80px'>
+ <h3>PolygonKiwii</h3>
+ <div class='by' style='font-style: italic;'></div>
+ <div class='comment_content'><p>Because radv isn't their driver and amdvlk shares its code with the windows driver.</p><p>But it's not that bad, as the biggest performance gains will likely come from optimizing llvm, which both drivers make use of*.</p><p>Also it's not a problem to install two Vulkan drivers side by side so users could always do that if they really need both.</p><p>* except for the pro stack, which uses a proprietary compiler shared with windows. I think their plan was to improve llvm and replace the proprietary compiler when llvm caught up in performance, but don't quote me on that</p></div>
+ </div>
+ </div>
+</div>
+</body>
git://git.nikiroo.be / gofetch.git / blobdiff