Revert "Abolish get_available_num_host_mem_channels" #400
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.
Reverts commit 3210bd9 from #393.
Issue
Metal CI failure tracked in tenstorrent/tt-metal#15675
Description
The reverted commit removed logic that allowed applications to request more hugepages than available to UMD. Previously, UMD would issue a warning in such cases. However, this created a potential safety issue since applications had no visibility into partial hugepage allocation (e.g., requesting 4 pages but receiving only 2).
This situation could lead to:
While the original change (making excessive hugepage requests a fatal error) improved safety, particularly in conjunction with IOMMU enablement, it caused failures in Metal CI tests that (possibly unintentionally?) request more hugepages than available. This revert is a temporary measure until the Metal CI tests can be updated.
List of the changes
Testing
CI
API Changes
There are no API changes in this PR.