FEP(sig-network): FlagCX new features for FlagOS 2.2 - #85
Open
wbavon wants to merge 6 commits into
Open
Conversation
Signed-off-by: wbtiger <28288271@qq.com>
Signed-off-by: wbtiger <28288271@qq.com>
Contributor
|
Design vendors to adapt FlagCX SVT test cases (new chip vendor with 9 comm operators,40 functions) |
Per the 2026-08-24 sync with development: - Owner set to @MC952-arch. - G2 names Kunlunxin as the first Device API vendor (PR ~09-10, second vendor carries schedule risk). - G3 PD disaggregation narrows to T-Head (1P+1D, 8+8 cards); the >=3% baseline is Mooncake TransferEngine default. MetaX becomes a stretch target: its base optimization is unfinished and GLM does not yet run there. - G4 states the actual status: adapted on NVIDIA, beats torch-native in most scenarios, Triton-distributed parity still being optimized; vendor scope this cycle is NVIDIA. - Ascend deferral (PCI-probe issue, tracked with the sglang-plugin Huawei P0) recorded under Non-Goals. - Test Plan adds the pre-testing inputs development provides (command doc, per-vendor API compatibility list) and the 2.2 scope rule; CI currently covers NVIDIA/MetaX/Hygon. - Related PRs adds the UIL groundwork (#539/#545) and the two pending vendor PRs. Unconfirmed items stay as TODO markers.
Collaborator
Author
|
recheck |
- The fused operators live in FlagTree, not FlagCX: python/tutorials/tle/raw/nvshmem/02-allgather-gemm and 03-gemm-allreduce. The FlagCX side of the feature is the Device API + IR bindings the kernels call. - The operators that exist are AllGather+GEMM and GEMM+AllReduce. Standalone AllGather/ReduceScatter and GEMM+ReduceScatter are not in the tree; moved to Non-Goals with a TODO to confirm scope. - G4's test row now uses the real harness: benchmark.py sweeps seven layer shapes at M=8192, gates correctness (atol/rtol 1e-3), times six variants against torch-native, and dumps a per-shape speedup CSV. - No Triton-distributed baseline exists anywhere in the tree; kept as TODO (add a third variant or run their upstream benchmark, version to be fixed) instead of claiming a comparison method. Signed-off-by: wbavon <wbtigergithub@126.com>
The development-side 2.2 feature list is the authoritative scope; the previous revision had narrowed Goals down to the 08-24 status snapshot. Now Goals state the committed targets and status is noted separately: - G3: PD disaggregation targets T-Head and MetaX (per the feature list); the 08-24 status stays — runs on T-Head at parity, MetaX gated on its base platform optimization. - G4: all four operators are in scope (AllGather, ReduceScatter, AllGather+GEMM, GEMM+ReduceScatter) with the Triton-distributed parity target. The verified FlagTree state stays: 02-allgather-gemm with its benchmark harness, 03-gemm-allreduce without one; standalone AG/RS and GEMM+RS have no located code yet and the Triton-distributed comparison method is undefined — both kept as TODOs, with test-plan rows carrying [TODO] rather than invented commands. - Non-Goals: GEMM+ReduceScatter and standalone AG/RS removed from the exclusion list (they are goals); MetaX removed from the PD exclusion. Signed-off-by: wbavon <wbtigergithub@126.com>
Collaborator
Author
|
recheck |
Remove the "Status 2026-08-24:" labels and similar framing from G3, G4, Features 2/3, and the G3/G4 test-plan intros; current state now reads as normal sentences in place. Collapse the duplicate 08-25 history entries into one. Signed-off-by: wbavon <wbtigergithub@126.com>
MC952-arch
reviewed
Aug 27, 2026
| 2. **PD-disaggregation support and optimization for inference** — run | ||
| prefill-decode disaggregation for GLM5.2 on T-Head and MetaX with ≥3% | ||
| end-to-end gain over the Mooncake TransferEngine baseline, building on the | ||
| P2P Engine introduced in v0.13.0 |
Contributor
There was a problem hiding this comment.
GLM5.2 PD分离测试目前仅在T-Head上跑通,后续高优开展优化工作,沐曦有风险
MC952-arch
reviewed
Aug 27, 2026
| ([FEP-0021](0021-flagcx-v0.13.0-new-features.md)). | ||
| 3. **Distributed operators** — AllGather and ReduceScatter, plus the fused | ||
| AllGather+GEMM and GEMM+ReduceScatter operators, targeting intra-node and | ||
| inter-node performance on par with Triton-distributed. |
MC952-arch
reviewed
Aug 27, 2026
| ([FEP-0021](0021-flagcx-v0.13.0-new-features.md)). | ||
| 3. **Distributed operators** — AllGather and ReduceScatter, plus the fused | ||
| AllGather+GEMM and GEMM+ReduceScatter operators, targeting intra-node and | ||
| inter-node performance on par with Triton-distributed. |
Contributor
There was a problem hiding this comment.
三组测试:
- intra/inter-node ReduceScatter
- intra/inter-node AllGather
- intra/inter-node GEMM+ReduceScatter
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
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.
FEP for the FlagCX features in the FlagOS 2.2 cycle, on top of v0.13.0:
02-allgather-gemmwith a benchmark harness vs. torch-native,03-gemm-allreduce); standalone AG/RS and GEMM+RS code locations plus the Triton-distributed comparison method are open TODOs.Test Plan carries the pre-testing inputs from development (official command doc, per-vendor API compatibility list — CI currently covers NVIDIA/MetaX/Hygon) and the 2.2 scope rule (existing features tested to 2.1 scope more thoroughly; new features only within the stated support scope).
Status stays
Provisionaluntil the open TODOs are filled: second Device API vendor, ≥3% metric definition, operator code locations, Triton-distributed baseline method. Owner: @MC952-arch. Feature Freeze 2026-08-31.