How zeux/volk works
volk is a C89 Vulkan meta-loader. An application includes volk.h, initializes the system Vulkan loader, creates a Vulkan instance, then loads instance entrypoints; after device creation it can load device functions globally or into a per-device table to reduce dispatch overhead. The graph separates loader bootstrap, instance loading, and device loading. The README documents this sequence and the optimization modes; the sampled volk.c excerpts show generated entrypoint loading, but not the initializer implementation.
Main entry points: volk.c Initialize loader · volk.h API and declarations
Components 9
Public API
- API and declarations
volk.h
Loader Bootstrap
- Initialize loader
volk.c - System Vulkan loader
Instance Loading
- Load instance functions
volk.c - Vulkan instance
Device Loading
- Load device functions
volk.c - Device function table
volk.h
Other components
- Vulkan Application
- Vulkan driver
Connections 9
- Vulkan Application → API and declarations: includes API
README.md - Vulkan Application → Initialize loader: calls initialize
README.md - Initialize loader → System Vulkan loader: loads from system
README.md - Vulkan Application → Vulkan instance: creates instance
README.md - Vulkan Application → Load instance functions: loads entrypoints
README.md - Load instance functions → Vulkan instance: uses instance
README.md - Vulkan Application → Load device functions: loads device functions
README.md - Load device functions → Vulkan driver: resolves functions
README.md - Vulkan Application → Device function table: uses per-device table
README.md