From: Brian Starkey <brian.starkey@arm.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, "Greg KH" <greg@kroah.com>,
"Jason Ekstrand" <jason.ekstrand@collabora.com>,
nd@arm.com, "Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH v4] dma-buf: Add a capabilities directory
Date: Tue, 7 Jun 2022 11:36:14 +0100 [thread overview]
Message-ID: <20220607103614.7ucvgdeprg4yv6li@000377403353> (raw)
In-Reply-To: <CAKMK7uEYncnjbwq6fQMNB_5tupMASrAFEadPg9xBS3ykNgNk4A@mail.gmail.com>
On Thu, Jun 02, 2022 at 08:47:56AM +0200, Daniel Vetter wrote:
>
> Two expand on this:
>
> - compositor opens the drm render /dev node
> - compositor initializes the opengl or vulkan userspace driver on top of that
> - compositor asks that userspace driver to allocate some buffer, which
> can be pretty expensive
> - compositor asks the userspace driver to export that buffer into a dma-buf
> - compositor can finally do the test ioctl, realizes support isn't
> there and tosses the entire thing
>
> read() on a sysfs file is so much more reasonable it's not even funny.
>
What about dma-buf heaps? That should be a shorter route to getting a
dma-buf fd if that's all that's needed.
Cheers,
-Brian
next prev parent reply other threads:[~2022-06-07 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 16:13 [PATCH v4] dma-buf: Add a capabilities directory Simon Ser
2022-06-01 16:51 ` Christian König
2022-06-01 18:05 ` Jason Ekstrand
2022-06-02 5:40 ` Greg KH
2022-06-02 6:17 ` Simon Ser
2022-06-02 6:25 ` Greg KH
2022-06-02 6:34 ` Simon Ser
2022-06-02 6:47 ` Daniel Vetter
2022-06-06 15:10 ` Robin Murphy
2022-06-06 15:22 ` Greg KH
2022-06-06 15:44 ` Robin Murphy
2022-06-07 10:36 ` Brian Starkey [this message]
2022-06-07 10:55 ` Greg KH
2022-06-07 14:52 ` Jason Ekstrand
2022-06-07 16:01 ` Greg KH
2022-06-08 15:15 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220607103614.7ucvgdeprg4yv6li@000377403353 \
--to=brian.starkey@arm.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=jason.ekstrand@collabora.com \
--cc=nd@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).