Pool of variable-size buffers

[Olivier Crête]

Hi,

Using a GstBufferPool is a valid option. One thing you can do is to
create entirely empty buffers (with no memories attached). You will
then need to implement a custom reset_memory vfunc on the bufferpool 
to reset the memory tag flag and separate the memories from the buffer
before calling up. Then you can create a custom GstAllocator that you
can use to get the GstMemory objects from, you can also pre-allocate
those (one for each of your buffers), then you can attach them to the
GstBuffer from the pool when you want to send something down the
pipeline. So your entire use-case can be done without doing a single
allocation!

Olivier


On Mon, 2016-12-05 at 20:00 +0100, Petr Kulhavy wrote:
> Hi,
> 
> I'm trying to implement an efficient buffer management for zero-copy
> UDP 
> reception, where the data is provided in chunks of memory
> preallocated 
> by the kernel.
> The unfortunate heavy-weight nature of GStreamer buffers, where
> every 
> buffer is a set of objects, is a bit clashing with the "efficient"
> part 
> of my task.
> 
> So I have the buffers of memory with data and now need to implement
> a 
> pool of GstBuffer and GstMemory objects in order to be able to hand
> over 
> the data down the pipeline. Kind of pool of empty buffers, where I
> can 
> then hang whatever chunk of memory I need.
> The buffer pool abstraction is based on the fact that all buffers are
> of 
> equal size. This is unfortunately not what I can guarantee.
> 
> Is there some existing abstraction I can use?
> 
> Thanks
> Petr
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
-- 
Olivier Crête
olivier.crete at collabora.com