<div dir="ltr">Thanks, guys. I will take a look at gstgl. </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 9, 2019 at 6:39 AM Nirbheek Chauhan <<a href="mailto:nirbheek.chauhan@gmail.com">nirbheek.chauhan@gmail.com</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Apr 8, 2019 at 7:40 AM Aaron Boxer <<a href="mailto:boxerab@gmail.com" target="_blank">boxerab@gmail.com</a>> wrote: > Is there any existing element I could use as a template? > One twist is that GPUs give the highest performance in asynchronous mode, so > the element will need to pull buffers from upstream, schedule them to > the GPU, and only push the processed buffers downstream when the GPU > completes. Also, it would be good to have the option of keeping the memory > on the device, in order to apply a series of kernels without costly move > to host and back to device. > The gstgl library does exactly all this. See, for example, inside gst-plugins-base/gst-libs/gst/gl/gstglwindow.c, gst_gl_window_default_send_message() which for instance runs all GL functions inside the glib main context attached to the window. You can probably do something similar. For keeping memory on the device, that's already supported by GstBuffer and by GstMemory, for instance GL and DMA-BUF memories are always on the device. You can add a new caps type for device-side compute buffers. Matthew (ystreet) might've spent some time on this already. Cheers, Nirbheek _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a></blockquote></div>