feat: expose CUDA device attributes - #255
Open
honeyspoon wants to merge 2 commits into
Open
Conversation
Signed-off-by: abder <bobmatt911@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Deviceexposes its L2 size, but querying related occupancy, bandwidth, and persisting-cache limits requires direct calls throughcuda_core::sys.What changed
DeviceAttributeenum.Device::attributeaccess to integer-valued CUDA device properties.l2_cache_size_bytesthrough the shared query path.This extends the existing
DeviceAPI only; it does not add context, stream, module, or launch abstractions.Validation
cargo fmt --all -- --checkcargo check -p cuda-core --all-targetscargo test -p cuda-core --test device_attributes --no-runcargo test -p cuda-core --doc