<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Massive slowdown under specific memcpy implementations (32bit, no-SIMD, backward copy)."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107670#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Massive slowdown under specific memcpy implementations (32bit, no-SIMD, backward copy)."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107670">bug 107670</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>(In reply to Timothy Arceri from <a href="show_bug.cgi?id=107670#c1">comment #1</a>)
<span class="quote">> There already is asm optimized version of memcpy() in glibc. Why would we
> want to reinvent that in Mesa?
>
> glibc should pick the right implementation for you system.</span >
How would memcpy() know that the destination is mapped to PCI-E address space
i.e. gets transparently transferred over the PCI-E bus (which has its own
performance constraints)?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>