This page is for version 5.0 (Latest) (default).
For other versions, use one of these documentation indexes:
- 5.0 (Latest) (default): https://docs.nvidia.com/holoscan/sdk-user-guide/5-0-latest/llms.txt
- ltsb-2.0: https://docs.nvidia.com/holoscan/sdk-user-guide/ltsb-2-0/llms.txt
- 4.6: https://docs.nvidia.com/holoscan/sdk-user-guide/4-6/llms.txt
- 4.5: https://docs.nvidia.com/holoscan/sdk-user-guide/4-5/llms.txt
- 4.4: https://docs.nvidia.com/holoscan/sdk-user-guide/4-4/llms.txt
- 4.3: https://docs.nvidia.com/holoscan/sdk-user-guide/4-3/llms.txt
- Archives: https://docs.nvidia.com/holoscan/sdk-user-guide/archives/llms.txt
Wrap existing tensor storage and attach it to a Holoscan tensor.
The release function is optional; when provided, it is called when the tensor releases the backing MemoryBuffer. A nonnegative device_id is a caller assertion that device storage belongs to that CUDA ordinal; this skips the CUDA pointer-attribute query used for validation. Leave it as Allocator::kUnknownDeviceId (the default) for unknown provenance so Tensor construction derives and validates the ordinal from the backing pointer when the storage type requires it.