synchronized-queue | A thread synchonized queue made for PThreads | Architecture library
kandi X-RAY | synchronized-queue Summary
kandi X-RAY | synchronized-queue Summary
A thread synchonized queue made for PThreads
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of synchronized-queue
synchronized-queue Key Features
synchronized-queue Examples and Code Snippets
Community Discussions
Trending Discussions on synchronized-queue
QUESTION
Trying to implement a produced consumer scenario where one process feeds cv::Mat objects into a queue buffer. And the consumer consumes them. cv::Mat has a settable allocator that can be implemented for custom memory management, but I had no success in making it work. Popping from the que on consumer side led to segfaults. The closest I've got is this implementation whwre cv::Mat is serialized and deserialized. Another downside of this implementation is buffer size is defined during compilation. So to reiterate the questions: how to efficiently implement cv::Mat lockfree queue in a shared memory.
Related questions:
...ANSWER
Answered 2020-Nov-18 at 20:24The "settable" allocator for cv::Mat
is NOT a Boost Interprocess allocator.
It looks like it's gonna be "hard" to implement the cv::Matallocator
interface to wrap one, as well.
This could be because the fancier allocators are intended for CUDA support, but I'm guessing a bit here.
So, I'd strongly suggest serializing. This should be okay unless you're dealing with giant matrices. See e.g.
Of course you can serialize to shared memory: https://www.boost.org/doc/libs/1_37_0/doc/html/interprocess/streams.html or https://www.boost.org/doc/libs/1_74_0/libs/iostreams/doc/quick_reference.html#devices
Now if you need large matrices (and they NEED to be OpenCV anyways) consider using existing CV allocators to allocate from an already existing contiguous buffer in your shared memory.
This could be as simple as just a vector >
or, indeed array
constructed inside shared memory (either managed (managed_shared_memory
) or unmanaged (bip::mapped_region
that works on top of bip::shared_memory_object
).
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install synchronized-queue
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page