Seungha Yang 30d06e03c2 cudamemory: Make GstCudaStream-aware ... This will be used for CUDA stream sharing. * Adding GstCudaPoolAllocator object. The pool allocator will control synchronization of allocated memory objects. * Modify gst_cuda_allocator_alloc() API so that caller can specify/set GstCudaStream object for the newly allocated memory. * GST_CUDA_MEMORY_TRANSFER_NEED_SYNC flag is added in addition to existing GST_CUDA_MEMORY_TRANSFER_NEED_{UPLOAD,DOWNLOAD}. The flag indicates that any GPU command queued in the CUDA stream may not be finished yet, and caller should take care of the synchronization. The flag is controlled by GstCudaMemory object if the memory holds GstCudaStream. (Otherwise, GstCudaMemory will do synchronization as before this commit). Specifically, GstCudaMemory object will set the new flag automatically when memory is mapped with (GST_MAP_CUDA | GST_MAP_WRITE) flags. Caller will need to unset the flag via GST_MEMORY_FLAG_UNSET() if it's already synchronized by client code. * gst_cuda_memory_sync() helper function is added to perform synchronization * Why not use CUevent object to keep track of synchronization status? CUDA provides fence-like interface already via CUevent object, but cuEventRecord/cuEventQuery APIs are not zero-cost operations. Instead, in this version, the status is tracked by using map and object flags. Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/3629>		2023-02-03 15:27:42 +00:00
..
gst	cudamemory: Make GstCudaStream-aware	2023-02-03 15:27:42 +00:00
meson.build	Move files from gst-plugins-bad into the "subprojects/gst-plugins-bad/" subdir	2021-09-24 16:14:36 -03:00