[Mesa-dev] [PATCH 0/4] drisw/glx: use XShm if possible

Marc-André Lureau marcandre.lureau at gmail.com
Thu Jun 11 06:46:44 PDT 2015

Hi Axel

On Thu, Jun 11, 2015 at 7:37 AM, Axel Davy <axel.davy at 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.


Marc-André Lureau
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20150611/062dfadc/attachment.html>

More information about the mesa-dev mailing list