Detect GOAL rank layout for HTSIM mapping#18
Merged
Conversation
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
1 participant
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.
This PR detects the GOAL rank layout used by the loaded binary, which lets HTSIM choose the correct rank-to-node assignment for V1 vs V2 generated traces.
The GOAL binary does not store an explicit generator version, so we infer the layout from the parsed header. V1 --unique-nic traces use NIC IDs to distinguish GPUs within a node, so HTSIM maps (rank, nic) to rank * num_nics + nic. V2 traces use GPU-rank layout, so HTSIM maps each GOAL rank directly to the HTSIM node.