Hi Hiro, I am not sure about the context of the comment you mentioned in gstreamer-vaapi, but VABuffer can be used as long as they have not been destroyed. The reason for vaUnmapBuffer() is that it will force host CPU cache flushes, before the driver operates on the buffer. The "SyncBuffer" you mentioned below basically achieves the same so I don't see a need to add a "SyncBuffer" function. Jonathan -----Original Message----- From: Hirokazu Honda <hiroh(a)chromium.org&gt; Sent: Sunday, October 27, 2019 8:41 PM To: intel-vaapi-media(a)lists.01.org Cc: Balachandran, Sreerenj <sreerenj.balachandran(a)intel.com&gt; Subject: [intel-vaapi-media] VABuffer is recyclable? Hi all. I am thinking to recycle VABuffers in video processing. A VABuffer created by vaCreateBuffer() intuitively only has to be destroyed when a buffer is no longer needed, that is, in the end of the processing. I checked gstreamer-vaapi code today. VABuffer used on video encoding is always created and destroyed in encoding each frame [1]. There is a comment. If this is true, we cannot reuse VABuffers during video processing. Besides, I am curious if we really need to vaUnmap before a driver reads a content modified by an application. VA-API documents vaUnamp needs to be called in order to notify a driver can consume the buffer by the driver [2]. But, in this way, we need to map/unmap in every buffer modification. I wonder if we can have SyncBuffer, similar to SyncSurface, to avoid map/unmap. What do you think? [1] https://github.com/GStreamer/gstreamer-vaapi/blob/1c3b02daf2fed53fa9ca726... [2] http://intel.github.io/libva/group__api__core.html#gae9b81871416c64b07e81... Thanks in advance, -Hiro _______________________________________________ intel-vaapi-media mailing list -- intel-vaapi-media(a)lists.01.org To unsubscribe send an email to intel-vaapi-media-leave(a)lists.01.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s