<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Performance improvement : Please consider hardware ɢᴘᴜ rendering in llvmpipe" href="https://bugs.freedesktop.org/show_bug.cgi?id=93686#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Performance improvement : Please consider hardware ɢᴘᴜ rendering in llvmpipe" href="https://bugs.freedesktop.org/show_bug.cgi?id=93686">bug 93686</a> from <a class="email" href="mailto:ytrezq@sdf-eu.org" title="ytrezq@sdf-eu.org">ytrezq@sdf-eu.org</a> <pre>(In reply to Marek Olšák from <a href="show_bug.cgi?id=93686#c18">comment #18</a>) > A fast GPU + slow GPU is also a bad idea. There is the risk of improper load > balancing resulting in the performance being the same or slightly above the > slow GPU. Or if it's done badly, it can be well below the slow GPU. So why mixing a ᴄᴘᴜ and a fast ɢᴘᴜ isn’t a problem in OpenCl ? > You are also completely missing the main use case for llvmpipe: to have > desktop compositing if an OpenGL driver isn't installed or doesn't exist. > Nobody cares about supercomputers. llvmpipe is essentially an opersource driver itself (the difference is only not requiring in‑kernel part). So generally when a modern Linux distro ship llvmpipe, it also makes sure Opensource drivers (with their kernel modules) for Nvidia ; Intel ; ᴀᴍᴅ are also installed and loaded. Hence the LIBGL_ALWAYS_SOFTWARE=1 so widely used on phoronix.com for benchmarking llvmpipe.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>