NIXLBENCH: Fix memory allocation for non OBJ/storage use case - #637
Merged
Merged
Conversation
|
👋 Hi iyastreb! Thank you for contributing to ai-dynamo/nixl. Your PR reviewers will review your contribution then trigger the CI to test your changes. 🚀 |
brminich
approved these changes
Jul 30, 2025
glevnv
approved these changes
Jul 30, 2025
Contributor
|
/build |
brminich
enabled auto-merge (squash)
July 30, 2025 06:56
ovidiusm
pushed a commit
to ovidiusm/nixl
that referenced
this pull request
Jul 30, 2025
pvijayakrish
pushed a commit
that referenced
this pull request
Jul 30, 2025
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
4 participants
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.
What?
The regression is introduced in #607, which leads to segfault, and nixlbench is not usable for non OBJ/storage use cases
Why?
remote_iovs are not populated in non OBJ/storage use cases