[PATCH] xwayland: Use drm buffers for cursors if available
ppaalanen at gmail.com
Fri Feb 5 12:53:57 UTC 2016
On Fri, 5 Feb 2016 13:13:16 +0100
Rui Tiago Cação Matos <tiagomatos at gmail.com> wrote:
> On Fri, Feb 5, 2016 at 9:42 AM, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> > Btw. Rui, is there a reason to keep the shm pool fd open after a
> > wl_buffer has been created from it? Most trivial demos just close the
> > fd and destroy the pool once a wl_buffer has been created, keeping only
> > the wl_buffer and the mmap around. The pool or fd are not needed to
> > keep the memory available to both the Wayland server and client. But if
> > you want to enlarge the pool, then you need the fd, naturally.
> Some X clients cause the X server to realize a huge number of cursors
> at the same time. For instance, to reach the fd limit I just need to
> open 2 instances of ImageMagick's display tool.
Sure, but why do you keep the fds open after you have created the
wl_buffer and mmapped the memory? What do you need the fd for, or the
You don't need the fd or the pool to write into the buffer, or attach
and commit the wl_buffer, or...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 811 bytes
Desc: OpenPGP digital signature
More information about the xorg-devel