https://bugs.freedesktop.org/show_bug.cgi?id=107670
--- Comment #19 from Michel Dänzer <mic...@daenzer.net> ---
Axel, I'm not sure what you're saying. Anyway, if the problem was that the
source of the memcpy is uncacheable, surely it would always be slow, regardless
of which memcpy implementation is used?
> So while it lists VRAM for the location, I'm not sure how the flag is used
> and if it affects the mapping.
RADEON_FLAG_GTT_WC means a write-combined CPU mapping will be used while the
buffer object resides in the GTT domain. CPU mappings of VRAM are always
write-combined.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
