You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are certain extensions like VK_AMD_shader_core_properties which could be useful in a compute scenario, as Vulkan does not (to my knowledge) provide an offical method of getting device information, for example the number of compute units. The information from VK_AMD_shader_core_properties could be exposed via vuh::Device with a function, for example
However I'm unsure if this is an approach that vuh would benefit from - it is specific to AMD devices and, while you could load it implicitly and then add runtime checks to the getShaderCorePropertiesAMD call (throwing an error if VK_AMD_shader_core_properties was not loaded), it might be better to have a more generic device information function. This could be implemented for AMD GPUs using VK_AMD_shader_core_properties, however that would only be possible if respective/similar extensions for Intel and Nvidia GPUs existed (I have not checked) and shared a "common" way of describing a GPU's internals, or enough information to provide the results in a generic manner - this is available to an extent with OpenCL (for example using CL_DEVICE_MAX_COMPUTE_UNITS), however even that is imperfect - for example, see https://stackoverflow.com/a/9326978.
The text was updated successfully, but these errors were encountered:
There are certain extensions like
VK_AMD_shader_core_properties
which could be useful in a compute scenario, as Vulkan does not (to my knowledge) provide an offical method of getting device information, for example the number of compute units. The information fromVK_AMD_shader_core_properties
could be exposed viavuh::Device
with a function, for exampleHowever I'm unsure if this is an approach that
vuh
would benefit from - it is specific to AMD devices and, while you could load it implicitly and then add runtime checks to thegetShaderCorePropertiesAMD
call (throwing an error ifVK_AMD_shader_core_properties
was not loaded), it might be better to have a more generic device information function. This could be implemented for AMD GPUs usingVK_AMD_shader_core_properties
, however that would only be possible if respective/similar extensions for Intel and Nvidia GPUs existed (I have not checked) and shared a "common" way of describing a GPU's internals, or enough information to provide the results in a generic manner - this is available to an extent with OpenCL (for example usingCL_DEVICE_MAX_COMPUTE_UNITS
), however even that is imperfect - for example, see https://stackoverflow.com/a/9326978.The text was updated successfully, but these errors were encountered: