OpenVDB
9.0.1
|
HostBuffer - a buffer that contains a shared or private bump pool to either externally or internally managed host memory. More...
#include <stdint.h>
#include <cstdio>
#include <cstdlib>
#include <memory>
#include <mutex>
#include <unordered_set>
#include <cassert>
#include <sstream>
#include <cstring>
Go to the source code of this file.
Classes | |
struct | BufferTraits< BufferT > |
class | HostBuffer |
This is a buffer that contains a shared or private pool to either externally or internally managed host memory. More... | |
struct | HostBuffer::Pool |
Namespaces | |
nanovdb | |
Macros | |
#define | checkPtr(ptr, msg) |
HostBuffer - a buffer that contains a shared or private bump pool to either externally or internally managed host memory.
This HostBuffer can be used in multiple ways, most of which are demonstrated in the examples below. Memory in the pool can be managed or unmanged (e.g. internal or external) and can be shared between multiple buffers or belong to a single buffer.
Example that uses HostBuffer::create inside io::readGrids to create a full self-managed buffer, i.e. not shared and without padding, per grid in the file.
Example that uses HostBuffer::createFull. Assuming you have a raw pointer to a NanoVDB grid of unknown type, this examples shows how to create its GridHandle which can be used to enquire about the grid type and meta data.
Example that uses HostBuffer::createPool for internally managed host memory. Suppose you want to read multiple grids in multiple files, but reuse the same fixed sized memory buffer to both avoid memory fragmentation as well as exceeding the fixed memory ceiling!
Example that uses HostBuffer::createPool for externally managed host memory. Note that in this example handles
are allowed to outlive pool
since they internally store a shared pointer to the memory pool. However data
MUST outlive handles
since the pool does not own its memory in this example.
Example that uses HostBuffer::createPool for externally managed host memory. Note that in this example handles
are allowed to outlive pool
since they internally store a shared pointer to the memory pool. However array
MUST outlive handles
since the pool does not own its memory in this example.
#define checkPtr | ( | ptr, | |
msg | |||
) |