-
Notifications
You must be signed in to change notification settings - Fork 30
Description
When targeting Vulkan, the size of a single buffer is often limited by maxMemoryAllocationSize and maxBufferSize to much less than the physical memory (most commonly ca. 2GB or 4GB, see vulkaninfo) .
It appears to me that NDBuffer is currently bound by the same limits.
It would be very convenient if either NDBuffer would internally lift this limit (probably by using multiple allocations) or if slangpy could provide an alternative container with an interface like NDBuffer that is not bound by the limit. The first option could be problematic since there may be implications to performance and memory continuity (although a guarantee to use a single buffer if possible and compiler optimizations in this special case may take care of that).
In particular if multiple different NDBuffer-like types are provided (but also in general), I would also appreciate an interface for get / set similar to ITensor and IRWTensor but without the differentiability constraint.