NVIDIA / NVIDIA/cutlass

[QST]Question About the Use of MMA In-Flight in SS_WarpSpecialized

Open
#2,074 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

? - Needs Triage inactive-30d inactive-90d question
Dominant language
C++
Stars
10.5k
Forks
2.1k
Avg merge
3d 11h
Merged PRs (30d)
7

Description

I don’t understand why MMA in-flight is used in SS_WarpSpecialized. As shown in the diagram below, I’ve illustrated my understanding with a pipeline diagram. If there is MMA in-flight, then after the computation of one stage is completed, the producer cannot immediately read the next set of values. Instead, it has to wait until the next MMA finishes before reading the current stage’s producer values. Does this waiting make sense?

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the SS_WarpSpecialized implementation and the pipeline diagram in the issue, focusing on where MMA in-flight is introduced. The issue does not identify a file, test, concrete code change, or completion criterion, so the expected outcome is not defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.