[Bug 691299] API: GstFileMemAllocator - an allocator that uses disk storage to provide memory space
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Wed Jul 17 17:51:06 PDT 2013
https://bugzilla.gnome.org/show_bug.cgi?id=691299
GStreamer | gstreamer (core) | git
--- Comment #6 from Krzysztof Konopko <krzysztof.konopko at gmail.com> 2013-07-18 00:51:02 UTC ---
(In reply to comment #4)
> I think the fd and other parameters should be part of the GstMemory and the
> allocator can be made a singleton then.
Making it a singleton was my first thought but then I faced scenarios when an
app (a long running process or a daemon if you like) created and destroyed
GStreamer pipelines quite frequently and I had to add an API to reset the
allocator (not included to the attached patch yet).
Passing fd sounds like an interesting idea.
> It should also be possible to e.g. let
> filesrc create such memory instead of only using it for random allocations. The
> name should probably be GstMappedFileMemory or GstMMapMemory.
Sure, I'm strongly considering this.
>
> Take a look at gst-plugins-base/gst-libs/gst/allocators btw, that already
> contains a dmabuf allocator which is very similar (but should be kept
> separate). Could you merge your allocator into that library too?
Thanks for the hint. I had a brief look and it seems like a good idea. I
noticed that I should review thread safety in the allocator (I didn't need it
at all in my use case due to locking at a different level).
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list