[Bug 707793] New: dmabuf allocator shouldn't a singleton

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=707793
  GStreamer | gst-plugins-base | git

           Summary: dmabuf allocator shouldn't a singleton
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: olivier.crete at ocrete.ca
         QAContact: gstreamer-bugs at lists.freedesktop.org
            Blocks: 682770,707534
     GNOME version: ---


Created an attachment (id=254509)
 View: https://bugzilla.gnome.org/attachment.cgi?id=254509
 Review: https://bugzilla.gnome.org/review?bug=707793&attachment=254509

dmabuf: Make it not a singleton

dmabuf memory is most often associated with a device. For example, in v4l2, the
format of the device can not be re-negotiated (one can't call VIDIOC_S_FMT)
until all buffers have been freed. So we need to have a way to track when all
buffers coming out of that device has been freed. This can't be tracked at the
GstBuffer level unless we set the NO_SHARE flag and lose zero-copy
functionality. My solution is to have the allocator do that, and that means
that you need one allocator object per device.

See bug #707534 for the complete solution.

This is about the API change, so it needs to be reviewed/decided before 1.2 is
out.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.