gpu-alloc
gpu-alloc copied to clipboard
Implementation agnostic memory allocator for Vulkan-like APIs
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4. Release notes Sourced from actions/checkout's releases. v4.0.0 What's Changed Update default runtime to node20 by @takost in actions/checkout#1436 Support fetching without the --progress option...
Updates the requirements on [bitflags](https://github.com/bitflags/bitflags) to permit the latest version. Release notes Sourced from bitflags's releases. 2.2.1 What's Changed Refactor attribute filtering to apply per-flag by @KodrAus in bitflags/bitflags#345 Prepare...
I've implemented dx12 suballocations in wgpu, but I was unable to use this crate for it due to the differences between vk and dx12's memory allocation strategies. Dx12 has you...
At the moment the following is done: ```rust #[repr(transparent)] pub struct AshMemoryDevice { device: Device, } impl AshMemoryDevice { pub fn wrap(device: &Device) -> &Self { unsafe { // Safe...
These general implementations may be useful for some users.
### Background: Hello, the Fuchsia project vendors crates from crates.io, and in order to do so we require explicit license files alongside the source code. Here is the policy: https://fuchsia.dev/fuchsia-src/contribute/governance/policy/open-source-licensing-policies?hl=en#licenses_and_tracking...
The Vulkan specification has text has `VkPhysicalDeviceLimits::bufferImageGranularity` which allows drivers to request that buffers and images are put in different memory pages. This is useful at least on Nvidia where...
It would be very useful to do multiple reads/writes in a single mapping session. Currently, `write_bytes` and `read_bytes` are limited to exactly one request. Case in question: laying out texture...
From the implementation perspective, I can see how align mask would be more convenient. But from the API perspective in the `Request`, it's not very nice. For one, it's not...