NVIDIA / NVIDIA/cutlass

[QST] in implicit gemm conv, why does not support split-k when group !=1 ?

Open
#2,049 5 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

Image
the file is include/cutlass/conv/device/implicit_gemm_convolution.h
in implicit gemm conv, why does not support split-k when group !=1 ?
is this for performance ?

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 with include/cutlass/conv/device/implicit_gemm_convolution.h and inspect how split-K support is conditioned on group count. Trace the surrounding convolution configuration to determine whether the restriction is performance-related; done means providing a maintainer-confirmed rationale, ideally with any relevant constraints documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
machine-learning, performance
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.