Skip to content

Fix misleading comments in commsOverlapBench overlap-pair-pgs (#222) - #222

Open
MogicianWu wants to merge 1 commit into
facebookresearch:mainfrom
MogicianWu:export-D103730559
Open

Fix misleading comments in commsOverlapBench overlap-pair-pgs (#222)#222
MogicianWu wants to merge 1 commit into
facebookresearch:mainfrom
MogicianWu:export-D103730559

Conversation

@MogicianWu

@MogicianWuMogicianWu commented May 4, 2026

Copy link
Copy Markdown

Summary:

Fix three comments in commsOverlapBench.py that incorrectly described the --overlap-pair-pgs feature as creating only "two" process groups. The code actually creates 1 + len(pair_collectives_list) PGs, supporting N concurrent collectives on separate streams. Updated comments to accurately reflect this behavior.

Reviewed By: dsjohns2

Differential Revision: D103730559

@MogicianWu
MogicianWu requested a review from louisfeng as a code ownerMay 4, 2026 21:02
@meta-clameta-claBot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 4, 2026
@meta-codesync

Copy link
Copy Markdown

@MogicianWu has exported this pull request. If you are a Meta employee, you can view the originating Diff in D103730559.

@meta-codesyncmeta-codesyncBot changed the title Fix misleading comments in commsOverlapBench overlap-pair-pgsFix misleading comments in commsOverlapBench overlap-pair-pgs (#222)May 4, 2026
MogicianWu added a commit to MogicianWu/param that referenced this pull request May 4, 2026
…okresearch#222)
Summary:
Fix three comments in commsOverlapBench.py that incorrectly described the --overlap-pair-pgs feature as creating only "two" process groups. The code actually creates 1 + len(pair_collectives_list) PGs, supporting N concurrent collectives on separate streams. Updated comments to accurately reflect this behavior.
Reviewed By: dsjohns2
Differential Revision: D103730559
@meta-codesyncmeta-codesyncBot changed the title Fix misleading comments in commsOverlapBench overlap-pair-pgs (#222)Fix misleading comments in commsOverlapBench overlap-pair-pgsMay 4, 2026
@meta-codesyncmeta-codesyncBot changed the title Fix misleading comments in commsOverlapBench overlap-pair-pgsFix misleading comments in commsOverlapBench overlap-pair-pgs (#222)May 5, 2026
MogicianWu added a commit to MogicianWu/param that referenced this pull request May 5, 2026
…okresearch#222)
Summary:
Fix three comments in commsOverlapBench.py that incorrectly described the --overlap-pair-pgs feature as creating only "two" process groups. The code actually creates 1 + len(pair_collectives_list) PGs, supporting N concurrent collectives on separate streams. Updated comments to accurately reflect this behavior.
Reviewed By: dsjohns2
Differential Revision: D103730559
…okresearch#222)
Summary:
Fix three comments in commsOverlapBench.py that incorrectly described the --overlap-pair-pgs feature as creating only "two" process groups. The code actually creates 1 + len(pair_collectives_list) PGs, supporting N concurrent collectives on separate streams. Updated comments to accurately reflect this behavior.
Reviewed By: dsjohns2
Differential Revision: D103730559
@meta-cla

meta-claBot commented May 20, 2026

Copy link
Copy Markdown

Hi @MogicianWu!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA SignedThis label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.fb-exportedmeta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@MogicianWu