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 720727 - plugins: optimize GLTextureUploadMeta for same native textures
plugins: optimize GLTextureUploadMeta for same native textures
Status: RESOLVED DUPLICATE of bug 769293
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 720336
Blocks:
 
 
Reported: 2013-12-19 10:11 UTC by Gwenole Beauchesne
Modified: 2016-10-04 11:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gwenole Beauchesne 2013-12-19 10:11:40 UTC
GLTextureUploadMeta process could be optimized in a way where the associated GstVaapiTexture to the native texture supplied by the user through _upload() could be cached.

Currently, even if the GLTextureUploadMeta is attached to the buffer during its creation in the parent pool, the _upload() function would check for an existing GstVaapiTexture locally only, i.e. in that specific meta instead of its active neighbours too (in the pool).

This means that, say that GLTextureUploadMeta TUM1 and TUM2 are respectively attached to buffers B1 and B2, if B1 is uploaded with Texture id Tex0, and so is B2 afterwards with the very same Texture id Tex0, then we are still have two separate GstVaapiTexture holders for the same native Tex0. This is extra memory storage we don't really want.

Imagine we create a pool of 8 buffers, that end up with underlying resources (e.g. FBO, pixmap) requirements for 1080p (thus, x8), this starts to add up for the very same Tex0.
Comment 1 Víctor Manuel Jáquez Leal 2016-09-23 11:38:42 UTC
If I understand correctly, this bug is a duplicate of bug 769293
Comment 2 Víctor Manuel Jáquez Leal 2016-10-04 11:46:56 UTC
I'm going to close this bug as a dup of bug 769293.

@Sree, if you feel this wrong, please re-open it.

*** This bug has been marked as a duplicate of bug 769293 ***