<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> <span class="fn">Timothy Arceri</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Massive slowdown under specific memcpy implementations (32bit, no-SIMD, backward copy)."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107670">bug 107670</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Massive slowdown under specific memcpy implementations (32bit, no-SIMD, backward copy)."
href="https://bugs.freedesktop.org/show_bug.cgi?id=107670#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - 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:t_arceri@yahoo.com.au" title="Timothy Arceri <t_arceri@yahoo.com.au>"> <span class="fn">Timothy Arceri</span></a>
</span></b>
<pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=107670#c6">comment #6</a>)
<span class="quote">> (In reply to Timothy Arceri from <a href="show_bug.cgi?id=107670#c1">comment #1</a>)
> > 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.
>
> 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)?</span >
"The slowdown could be observed if non-SIMD version of the glibc-2.27 function
is used (like the one that comes with the 32 bit Slackware-current).
....
Using SSE2 memcpy seems to avoid this problem"
Glib should select the SSE2 (or better) version of memcpy. If Slackware doesn't
ship and SSE2 support for glibc I don't see how this is Mesas fault.
If I'm misunderstanding somthing please clarify. Otherwise I'm inclined to
close this as won't fix.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>