Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UCP/ADDRV2: BW lanes selection fixes - v1.15.x #9236

Merged
merged 2 commits into from
Aug 5, 2023

Conversation

brminich
Copy link
Contributor

What

  • Device num_paths coefficient should be applied after fp8 pack/unpack. Otherwise the ratio effect maybe just hidden by fp8 inaccuracy
  • When deciding what rma bw lanes to drop, local bw value needs to be packed/unpacked in fp8 format to make sure both sides make the same decision

Why ?

To avoid ep reconfiguration issues, because of assymetrical selection

When deciding what rma bw lanes to drop, local bw value needs to be
packed/unpacked in fp8 format to make sure both sides make the same
decision
Device num_paths coefficient should be applied after
fp8 pack/unpack. Otherwise the ratio effect maybe just hidden
by fp8 inaccuracy
@brminich brminich changed the title UCP/ADDRV2: BW lanes selection fixes UCP/ADDRV2: BW lanes selection fixes - v1.15.x Jul 25, 2023
@Alexey-Rivkin
Copy link
Collaborator

/azp run perf

@azure-pipelines
Copy link

No commit pushedDate could be found for PR 9236 in repo openucx/ucx

@yosefe
Copy link
Contributor

yosefe commented Jul 30, 2023

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s), but failed to run 1 pipeline(s).

@yosefe yosefe merged commit dcb293f into openucx:v1.15.x Aug 5, 2023
104 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants