bufferpool: is it possible wait all memory writalbe, nor free the buffer?

[Bing Song]

Hi Nicolas,

Sorry for ask the issue again.

Our use case implement one allocator based on V4L2, but use default GstVideoBufferPool. So can't handle flushing in allocator unless we implement video buffer pool based on V4L2. (we haven't use V4L2 allocator and V4L2 buffer pool released by Gstreamer as some limitation of V4L2 driver on our platform)

I prefer hook original buffer life time to the new buffer. Do you have patch for it? If no, I can try to generate patch for the solution. What's your opinion?

Regards,
Song Bing.

-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of Nicolas Dufresne
Sent: Friday, January 09, 2015 10:38 PM
To: gstreamer-devel at lists.freedesktop.org
Subject: Re: bufferpool: is it possible wait all memory writalbe, nor free the buffer?


Le 2015-01-09 04:50, Sebastian Dröge a écrit :
>> >I know the methods can fix my issue. But free and allocate buffer in video buffer pool isn't expect behave in some use case. Is it valuable to implement the feature in gstbufferpool.c?
> If you find a way how to implement that in a generic way, sure:)

That could be a way to solve the case where we discard buffers after
gst_buffer_make_writable() is called. A simpler plausible solution I had in mind, was to hook original buffer life time to the new buffer (in the case the memory are just reffed). I have not done any test of this.

Nicolas
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel