| Safe Haskell | None |
|---|---|
| Language | Haskell2010 |
Graphics.Vulkan.Core10.PipelineCache
- newtype VkPipelineCacheCreateFlags = VkPipelineCacheCreateFlags VkFlags
- type VkPipelineCache = Ptr VkPipelineCache_T
- vkCreatePipelineCache :: ("device" ::: VkDevice) -> ("pCreateInfo" ::: Ptr VkPipelineCacheCreateInfo) -> ("pAllocator" ::: Ptr VkAllocationCallbacks) -> ("pPipelineCache" ::: Ptr VkPipelineCache) -> IO VkResult
- vkDestroyPipelineCache :: ("device" ::: VkDevice) -> ("pipelineCache" ::: VkPipelineCache) -> ("pAllocator" ::: Ptr VkAllocationCallbacks) -> IO ()
- vkGetPipelineCacheData :: ("device" ::: VkDevice) -> ("pipelineCache" ::: VkPipelineCache) -> ("pDataSize" ::: Ptr CSize) -> ("pData" ::: Ptr ()) -> IO VkResult
- vkMergePipelineCaches :: ("device" ::: VkDevice) -> ("dstCache" ::: VkPipelineCache) -> ("srcCacheCount" ::: Word32) -> ("pSrcCaches" ::: Ptr VkPipelineCache) -> IO VkResult
- data VkPipelineCacheCreateInfo = VkPipelineCacheCreateInfo {
- vkSType :: VkStructureType
- vkPNext :: Ptr ()
- vkFlags :: VkPipelineCacheCreateFlags
- vkInitialDataSize :: CSize
- vkPInitialData :: Ptr ()
Documentation
newtype VkPipelineCacheCreateFlags Source #
VkPipelineCacheCreateFlags - Reserved for future use
Description
VkPipelineCacheCreateFlags is a bitmask type for setting a mask, but
is currently reserved for future use.
See Also
Constructors
| VkPipelineCacheCreateFlags VkFlags |
Instances
type VkPipelineCache = Ptr VkPipelineCache_T Source #
VkPipelineCache - Opaque handle to a pipeline cache object
Description
See Also
vkCreateComputePipelines,
vkCreateGraphicsPipelines,
vkCreatePipelineCache, vkDestroyPipelineCache,
vkGetPipelineCacheData, vkMergePipelineCaches
vkCreatePipelineCache :: ("device" ::: VkDevice) -> ("pCreateInfo" ::: Ptr VkPipelineCacheCreateInfo) -> ("pAllocator" ::: Ptr VkAllocationCallbacks) -> ("pPipelineCache" ::: Ptr VkPipelineCache) -> IO VkResult Source #
vkCreatePipelineCache - Creates a new pipeline cache
Parameters
deviceis the logical device that creates the pipeline cache object.
pCreateInfois a pointer to aVkPipelineCacheCreateInfostructure that contains the initial parameters for the pipeline cache object.pAllocatorcontrols host memory allocation as described in the Memory Allocation chapter.pPipelineCacheis a pointer to aVkPipelineCachehandle in which the resulting pipeline cache object is returned.
Description
Note
Applications can track and manage the total host memory size of a
pipeline cache object using the pAllocator. Applications can limit
the amount of data retrieved from a pipeline cache object in
vkGetPipelineCacheData. Implementations should not internally limit
the total number of entries added to a pipeline cache object or the
total host memory consumed.
Once created, a pipeline cache can be passed to the
vkCreateGraphicsPipelines and vkCreateComputePipelines commands. If
the pipeline cache passed into these commands is not
VK_NULL_HANDLE, the implementation
will query it for possible reuse opportunities and update it with new
content. The use of the pipeline cache object in these commands is
internally synchronized, and the same pipeline cache object can be
used in multiple threads simultaneously.
Note
Implementations should make every effort to limit any critical
sections to the actual accesses to the cache, which is expected to be
significantly shorter than the duration of the
vkCreateGraphicsPipelines and vkCreateComputePipelines commands.
Valid Usage (Implicit)
devicemust be a validVkDevicehandle
pCreateInfomust be a valid pointer to a validVkPipelineCacheCreateInfostructure- If
pAllocatoris notNULL,pAllocatormust be a valid pointer to a validVkAllocationCallbacksstructure pPipelineCachemust be a valid pointer to aVkPipelineCachehandle
Return Codes
- Success
- -
VK_SUCCESS
- Failure
- -
VK_ERROR_OUT_OF_HOST_MEMORYVK_ERROR_OUT_OF_DEVICE_MEMORY
See Also
VkAllocationCallbacks,
VkDevice,
VkPipelineCache, VkPipelineCacheCreateInfo
vkDestroyPipelineCache :: ("device" ::: VkDevice) -> ("pipelineCache" ::: VkPipelineCache) -> ("pAllocator" ::: Ptr VkAllocationCallbacks) -> IO () Source #
vkDestroyPipelineCache - Destroy a pipeline cache object
Parameters
deviceis the logical device that destroys the pipeline cache object.
pipelineCacheis the handle of the pipeline cache to destroy.pAllocatorcontrols host memory allocation as described in the Memory Allocation chapter.
Description
Valid Usage
- If
VkAllocationCallbackswere provided whenpipelineCachewas created, a compatible set of callbacks must be provided here
- If no
VkAllocationCallbackswere provided whenpipelineCachewas created,pAllocatormust beNULL
Valid Usage (Implicit)
devicemust be a validVkDevicehandle
- If
pipelineCacheis notVK_NULL_HANDLE,pipelineCachemust be a validVkPipelineCachehandle - If
pAllocatoris notNULL,pAllocatormust be a valid pointer to a validVkAllocationCallbacksstructure - If
pipelineCacheis a valid handle, it must have been created, allocated, or retrieved fromdevice
Host Synchronization
- Host access to
pipelineCachemust be externally synchronized
See Also
vkGetPipelineCacheData :: ("device" ::: VkDevice) -> ("pipelineCache" ::: VkPipelineCache) -> ("pDataSize" ::: Ptr CSize) -> ("pData" ::: Ptr ()) -> IO VkResult Source #
vkGetPipelineCacheData - Get the data store from a pipeline cache
Parameters
deviceis the logical device that owns the pipeline cache.
pipelineCacheis the pipeline cache to retrieve data from.pDataSizeis a pointer to a value related to the amount of data in the pipeline cache, as described below.pDatais eitherNULLor a pointer to a buffer.
Description
If pData is NULL, then the maximum size of the data that can be
retrieved from the pipeline cache, in bytes, is returned in pDataSize.
Otherwise, pDataSize must point to a variable set by the user to the
size of the buffer, in bytes, pointed to by pData, and on return the
variable is overwritten with the amount of data actually written to
pData.
If pDataSize is less than the maximum size that can be retrieved by
the pipeline cache, at most pDataSize bytes will be written to
pData, and vkGetPipelineCacheData will return VK_INCOMPLETE. Any
data written to pData is valid and can be provided as the
pInitialData member of the VkPipelineCacheCreateInfo structure
passed to vkCreatePipelineCache.
Two calls to vkGetPipelineCacheData with the same parameters must
retrieve the same data unless a command that modifies the contents of
the cache is called between them.
Applications can store the data retrieved from the pipeline cache, and
use these data, possibly in a future run of the application, to populate
new pipeline cache objects. The results of pipeline compiles, however,
may depend on the vendor ID, device ID, driver version, and other
details of the device. To enable applications to detect when previously
retrieved data is incompatible with the device, the initial bytes
written to pData must be a header consisting of the following
members:
+----+--------------+--------------------------------------------------+ | Of | Size | Meaning | | fs | | | | et | | | +====+==============+==================================================+ | 0 | 4 | length in bytes of the entire pipeline cache | | | | header written as a stream of bytes, with the | | | | least significant byte first | +----+--------------+--------------------------------------------------+ | 4 | 4 | a | | | | 'Graphics.Vulkan.Core10.Constants.VkPipelineCach | | | | eHeaderVersion' | | | | value written as a stream of bytes, with the | | | | least significant byte first | +----+--------------+--------------------------------------------------+ | 8 | 4 | a vendor ID equal to | | | | @VkPhysicalDeviceProperties@::@vendorID@ written | | | | as a stream of bytes, with the least significant | | | | byte first | +----+--------------+--------------------------------------------------+ | 12 | 4 | a device ID equal to | | | | @VkPhysicalDeviceProperties@::@deviceID@ written | | | | as a stream of bytes, with the least significant | | | | byte first | +----+--------------+--------------------------------------------------+ | 16 | @VK_UUID_SIZ | a pipeline cache ID equal to | | | E@ | @VkPhysicalDeviceProperties@::@pipelineCacheUUID | | | | @ | +----+--------------+--------------------------------------------------+ Layout for pipeline cache header version @VK_PIPELINE_CACHE_HEADER_VERSION_ONE@
The first four bytes encode the length of the entire pipeline cache header, in bytes. This value includes all fields in the header including the pipeline cache version field and the size of the length field.
The next four bytes encode the pipeline cache version, as described for
VkPipelineCacheHeaderVersion. A
consumer of the pipeline cache should use the cache version to
interpret the remainder of the cache header.
If pDataSize is less than what is necessary to store this header,
nothing will be written to pData and zero will be written to
pDataSize.
Valid Usage (Implicit)
devicemust be a validVkDevicehandle
pipelineCachemust be a validVkPipelineCachehandlepDataSizemust be a valid pointer to asize_tvalue- If the value referenced by
pDataSizeis not0, andpDatais notNULL,pDatamust be a valid pointer to an array ofpDataSizebytes pipelineCachemust have been created, allocated, or retrieved fromdevice
Return Codes
- Success
- -
VK_SUCCESSVK_INCOMPLETE
- Failure
- -
VK_ERROR_OUT_OF_HOST_MEMORYVK_ERROR_OUT_OF_DEVICE_MEMORY
See Also
vkMergePipelineCaches :: ("device" ::: VkDevice) -> ("dstCache" ::: VkPipelineCache) -> ("srcCacheCount" ::: Word32) -> ("pSrcCaches" ::: Ptr VkPipelineCache) -> IO VkResult Source #
vkMergePipelineCaches - Combine the data stores of pipeline caches
Parameters
deviceis the logical device that owns the pipeline cache objects.
dstCacheis the handle of the pipeline cache to merge results into.srcCacheCountis the length of thepSrcCachesarray.pSrcCachesis an array of pipeline cache handles, which will be merged intodstCache. The previous contents ofdstCacheare included after the merge.
Description
Note
The details of the merge operation are implementation dependent, but implementations should merge the contents of the specified pipelines and prune duplicate entries.
Valid Usage
dstCachemust not appear in the list of source caches
Valid Usage (Implicit)
devicemust be a validVkDevicehandle
dstCachemust be a validVkPipelineCachehandlepSrcCachesmust be a valid pointer to an array ofsrcCacheCountvalidVkPipelineCachehandlessrcCacheCountmust be greater than0dstCachemust have been created, allocated, or retrieved fromdevice- Each element of
pSrcCachesmust have been created, allocated, or retrieved fromdevice
Host Synchronization
- Host access to
dstCachemust be externally synchronized
Return Codes
- Success
- -
VK_SUCCESS
- Failure
- -
VK_ERROR_OUT_OF_HOST_MEMORYVK_ERROR_OUT_OF_DEVICE_MEMORY
See Also
data VkPipelineCacheCreateInfo Source #
VkPipelineCacheCreateInfo - Structure specifying parameters of a newly created pipeline cache
Description
Valid Usage
- If
initialDataSizeis not0, it must be equal to the size ofpInitialData, as returned byvkGetPipelineCacheDatawhenpInitialDatawas originally retrieved
- If
initialDataSizeis not0,pInitialDatamust have been retrieved from a previous call tovkGetPipelineCacheData
Valid Usage (Implicit)
sTypemust beVK_STRUCTURE_TYPE_PIPELINE_CACHE_CREATE_INFO
pNextmust beNULLflagsmust be0- If
initialDataSizeis not0,pInitialDatamust be a valid pointer to an array ofinitialDataSizebytes
See Also
VkPipelineCacheCreateFlags,
VkStructureType, vkCreatePipelineCache
Constructors
| VkPipelineCacheCreateInfo | |
Fields
| |