bdwgc
VulkanMemoryAllocator
bdwgc | VulkanMemoryAllocator | |
---|---|---|
14 | 11 | |
2,795 | 2,383 | |
- | 0.7% | |
9.7 | 8.2 | |
2 days ago | 1 day ago | |
C | C | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bdwgc
-
Writing a Simple Garbage Collector in C (2020)
Boehm GC is mentioned in the article: https://github.com/ivmai/bdwgc
- Boehm-Demers-Weiser Garbage Collector
- Sound like some C stuff
-
Tricking the garbage collector with unsigned longs?
This stuff is all implementation dependent. The Boehm garbage collector has been wrestling with the compilers for years regarding these issues, see its development repo.
-
Any good resources to learn how to implement Automated Reference Counting in C99?
Any kind of automatic GC is going to be rare in C. The only automatic garbage collection that I am aware of is the BDW garbage collector abet that uses mark and sweep instead of reference counting https://github.com/ivmai/bdwgc
- Why isn't there a GCed variant of C++ that'd be functionally like Java, but with C++'s syntax?
-
Small (EXPERIMENTAL RESEARCH) project I made to add a reference counter GC to clang (specifically clang, will change) C
My dude have you heard of Boehm GC
VulkanMemoryAllocator
-
Why do I need to load VMA vulkan functions dynamically?
Hello - working on a Vulkan renderer and I ran into a topic I don't understand. I use the Vulkan Memory Allocator and upon updating my local targeted Vulkan SDK to 1.3.250 from 1.3.204, I receive exactly the same error as this user: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator/issues/280 Error: The procedure entry point vkGetDeviceBufferMemoryRequirements could not be located in the DLL.
-
Managing Vertex Buffers
For problem 1 I would recommend looking into Vulkan Memory Allocator: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator The general idea is to allocate large chunks of memory, then sub-allocate out of those when buffers are required. This is nice for several reasons: - Memory allocation can be slow and involve system calls. Sub-allocating does not require system calls - Your memory will be more cache-friendly as all your buffers will be relatively adjacent - There is a finite number of unique allocations you can have. Performing larger allocations keeps your usage lower
-
[Part 7] Update of my Vulkan renderer: LODs, Multiple different meshes, Memory Allocator, Render architecture and more
Integrated Vulkan Memory Allocator, making all GPU memory allocations much easier to work with.
-
Is it a good idea to use VMA for memory management for production?
Seems like it was initially added more than 2 years ago, they really should release more often :P
-
Vulkan 1.3 released
Use VMA, originally created by AMD, never worry about device memory and device memory alignment again.
-
Low bandwidth using memcpy
I am using VMA for memory allocation with the VMA_MEMORY_USAGE_GPU_TO_CPU usage flag. That means that the flags VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT and VK_MEMORY_PROPERTY_HOST_CACHED_BIT are already set.
-
Need advices over OpenGL/Vulkan abstraction
Repo for Vulkan Memory mangement (AMD): https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
-
Deleting staging buffer after copying to image causes weird artifacts in texture mapping
Since it's a header-only lib, you could always try cloning the latest from [GitHub](https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator) and see if the problem continues with that version.
-
Allocating multi-layered images with a huge amount of layers
Alternatively, you could just use an existing allocator library, a popular choice is VMA: https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator
-
Memory management doubts
Personally, I'd recommend (VMA)[https://github.com/GPUOpen-LibrariesAndSDKs/VulkanMemoryAllocator] if you don't want to deal with all of this yourself.
What are some alternatives?
nixos-flake-example - This is a demo NixOS config, with optional flakes support. Along with notes on why flakes is useful and worth adopting.
volk - Meta loader for Vulkan API
mmtk-core - Memory Management ToolKit
buddy_alloc - A single header buddy memory allocator for C & C++
kcgi - minimal CGI and FastCGI library for C/C++
doon-vk - Personal exploration of the Vulkan API
lisp - A mini Lisp in 1k lines of C with garbage collector, explained. Includes over 40 built-in Lisp primitives, floating point, strings, closures with lexical scope, macros, proper tail recursion, exceptions, execution tracing, file loading, a mark-sweep/compacting garbage collector and REPL.
vulkan-guide - Introductory guide to vulkan.
reproc - A cross-platform (C99/C++11) process library
SPP
nix - Nix, the purely functional package manager
OCRA - Overly Complicated Rendering Abstraction