[Bug 779145] dmabuf export from vaapi encoders fails

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=779145

Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nicolas at ndufresne.ca

--- Comment #8 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Scott D Phillips from comment #3)
> (In reply to Scott D Phillips from comment #2)
> > Created attachment 347176 [details] [review] [review]
> > [PATCH gst-plugins-base] fdmemory: Virtually dispatch get_fd through the
> > allocator
> > 
> > Change get_fd to be dispatched to the mem's allocator. This allows
> > subclasses of fdmemory to manipulate the fd throughout the
> > memory's lifetime in case the fd needs to come and go while the
> > backing memory itself lives.
> 
> This is some groundwork for changing the vaapi allocator to support
> releasing the dmabuf fd before doing a vaBeginPicture. In this idea, the
> vaapi allocator would inherit from dmabuf_allocator, but provide its own
> gstmemory which is back by a VASurface and only holds a dmabuf fd
> transiently.

Bad idea flag here. This will break all the caching we have implemented for
zero-copy path with DMABuf.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.