On Wed, 27 Jan 2021 12:01:55 +0100 Christian König <christian.koenig@xxxxxxx> wrote: > Somewhat correct. This interface here really doesn't make sense since > the file descriptor representation of DMA-buf is only meant to be used > for short term usage. > > E.g. the idea is that you can export a DMA-buf fd from your device > driver, transfer that to another process and then import it again into a > device driver. > > Keeping a long term reference to a DMA-buf fd sounds like a design bug > in userspace to me. Except keeping the fd is exactly what userspace must do if it wishes to re-use the buffer without passing a new fd over IPC again. Particularly Wayland compositors need to keep the client buffer dmabuf fd open after receiving it, so that they can re-import it to EGL to ensure updated contents are correctly flushed as EGL has no other API for it. That is my vague understanding, and what Weston implements. You can say it's a bad userspace API design in EGL, but what else can we do? However, in the particular case of Wayland, the shared dmabufs should be accounted to the Wayland client process. OOM-killing the client process will eventually free the dmabuf, also the Wayland server references to it. Killing the Wayland server (compositor, display server) OTOH is something that should not be done as long as there are e.g. Wayland clients to be killed. Unfortunately(?), Wayland clients do not have a reason to keep the dmabuf fd open themselves, so they probably close it as soon as it has been sent to a display server. So the process that should be OOM-killed does not have an open fd for the dmabuf (but probably has something else, but not an mmap for CPU). Buffer re-use in Wayland does not require re-sending the dmabuf fd over IPC. (In general, dmabufs are never mmapped for CPU. They are accessed by devices.) Thanks, pq
Attachment:
pgpyRZ7fPONgf.pgp
Description: OpenPGP digital signature
