VkDeviceMemory(3)
C Specification
A Vulkan device operates on data in device memory via memory objects that
are represented in the API by a VkDeviceMemory
handle:
// Provided by VK_VERSION_1_0
VK_DEFINE_NON_DISPATCHABLE_HANDLE(VkDeviceMemory)
See Also
VK_DEFINE_NON_DISPATCHABLE_HANDLE, VK_VERSION_1_0, VkBindAccelerationStructureMemoryInfoNV, VkBindBufferMemoryInfo, VkBindDataGraphPipelineSessionMemoryInfoARM, VkBindImageMemoryInfo, VkBindTensorMemoryInfoARM, VkBindVideoSessionMemoryInfoKHR, VkDeviceMemoryOpaqueCaptureAddressInfo, VkExportMetalBufferInfoEXT, VkMappedMemoryRange, VkMemoryGetAndroidHardwareBufferInfoANDROID, VkMemoryGetFdInfoKHR, VkMemoryGetMetalHandleInfoEXT, VkMemoryGetRemoteAddressInfoNV, VkMemoryGetWin32HandleInfoKHR, VkMemoryGetZirconHandleInfoFUCHSIA, VkMemoryMapInfo, VkMemoryUnmapInfo, VkSparseImageMemoryBind, VkSparseMemoryBind, VkTileMemoryBindInfoQCOM, VkWin32KeyedMutexAcquireReleaseInfoKHR, VkWin32KeyedMutexAcquireReleaseInfoNV, vkAllocateMemory, vkBindBufferMemory, vkBindImageMemory, vkFreeMemory, vkGetDeviceMemoryCommitment, vkGetMemoryWin32HandleNV, vkMapMemory, vkSetDeviceMemoryPriorityEXT, vkUnmapMemory
Document Notes
For more information, see the Vulkan Specification.
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.