Module vulkan
Available on crate feature 
unstable-wgpu-27 only.Expand description
Vulkan API internals.
§Vulkan API internals.
§Stack memory
Ash expects slices, which we don’t generally have available. We cope with this requirement by the combination of the following ways:
- temporarily allocating Vecon heap, where overhead is permitted
- growing temporary local storage
§Framebuffers and Render passes
Render passes are cached on the device and kept forever.
Framebuffers are also cached on the device, but they are removed when any of the image views (they have) gets removed. If Vulkan supports image-less framebuffers, then the actual views are excluded from the framebuffer key.
§Fences
If timeline semaphores are available, they are used 1:1 with wgpu-hal fences.
Otherwise, we manage a pool of VkFence objects behind each hal::Fence.
!
Structs§
- AccelerationStructure 
- Adapter
- Api
- BindGroup 
- BindGroup Layout 
- Buffer
- CommandBuffer 
- CommandEncoder 
- ComputePipeline 
- CreateDevice Callback Args 
- Arguments to the CreateDeviceCallback.
- CreateInstance Callback Args 
- Arguments to the CreateInstanceCallback.
- DebugUtils Create Info 
- DebugUtils Messenger User Data 
- User data needed by instance::debug_utils_messenger_callback.
- Device
- Instance
- InstanceShared 
- PhysicalDevice Features 
- Features supported by a [vk::PhysicalDevice] and its extensions.
- PipelineCache 
- PipelineLayout 
- QuerySet 
- Queue
- RenderPipeline 
- Sampler
- Surface
- SurfaceTexture 
- Texture
- TextureView 
- Workarounds
- Workaround flags.
Enums§
- Fence
- The Api::Fencetype forvulkan::Api.
- ShaderModule 
Type Aliases§
- CreateDevice Callback 
- Callback to allow changing the vulkan device creation parameters.
- CreateInstance Callback 
- Callback to allow changing the vulkan instance creation parameters.