Hi Axel
On Thu, Jun 11, 2015 at 7:37 AM, Axel Davy axel.d...@ens.fr wrote:
XPutImage requires to copy the images around, and the request may be
split over several chunks. Using XShm should improve performance.
Another way of doing that is to make the swrast loader allocate the
buffers,
and have swrast swap buffers instead of copying content.
For example there could be a request to allocate a first buffer,
and then a request to present an already allocated buffer, which
would return a new buffer (could be the same).
Doing that way, it could use XShm behind the scene, and it would fit
different usages, like having a zero copy mechanism for wayland swrast.
I thought about that, however I don't see how you could wait for X to
release the buffer, but to sync, because you can't have a private X event
handler. So effectively, it would use only a single buffer. Also I could
use guidance to design such an interface. Perhaps doing this on wayland
swrast would help defining it though.
regards
--
Marc-André Lureau
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
