Open SimLeek opened 7 months ago
This would be a relatively simple change, however it can end up quite manual due to the conversion logic required to return as a dict - the list of device options (incl devicelimits) are quite extensive so it would not be very feasible to try to encompass all. How are you currently getting this?
For completness, this is the code:
I'm currently getting it with some old code I use to try and get VkPhysicalDeviceProperties2
with using pyvulkan. It's extremely messy...
I agree it'd be too much to try to get all the items, but I think maxComputeSharedMemorySize
specifically is important enough that it should be included, even if it is mainly important for setting shared arrays using spec consts. Right now I need it for a reduction operation to a small array rather than to a single value.
Ok we can explore addijg these as they become required, but indeed it seems like although pyvulkan is not optimal, it may not be the worse option as it would cover exhaustive options - however happy for this to be extended. Would you be up for opening a PR?
Yep! It might take me a bit to get to though.
kp.Manager().get_device_properties()
theoretically has access tomaxComputeSharedMemorySize
throughVkPhysicalDeviceLimits
, but it's not given in Python.I need to get
maxComputeSharedMemorySize
to make sure the spec_consts I'm sending don't end up initializing a shared array that's larger than the GPU can handle. Right now I have to get that variable with another vulkan library.(Might make a pull request for this. Recording it now as a feature request so it's not lost.)