After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 752961 - glupload: Raw upload could be optimized using a BufferPool
glupload: Raw upload could be optimized using a BufferPool
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-07-28 13:15 UTC by Nicolas Dufresne (ndufresne)
Modified: 2018-11-03 11:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolas Dufresne (ndufresne) 2015-07-28 13:15:33 UTC
Currently when doing raw upload, we create a new GstBuffer and set of new texture every time we receives an input. This could be slightly optimized by reusing the textures through a BufferPool.

Note that a mechanism would be needed to properly attach the mapped input buffer so the buffer pool can detach it when the buffer comes back to the pool. What I would saggest is to add a method to attach the user_data/GDestroyNotify pair as qdata to each memory using a well known name. Then the pool reset() method could remove this qdata on each memory. The destroy notify would also be called if the memory is destroyed outside of the buffer.
Comment 1 GStreamer system administrator 2018-11-03 11:39:35 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/209.