tilegym-adding-cutile-kernel
NVIDIA/skills
Adicionar um novo operador de kernel de GPU cuTile ao TileGym, abrangendo o registro de despacho, a implementação do backend, as exportações, os testes e os benchmarks.
...Expandir tudoAdicionando um kernel cuTile ao TileGym
Fluxo de trabalho completo para adicionar um novo operador (por exemplo, my_op) com o backend cuTile.
Regras de execução
É OBRIGATÓRIO seguir rigorosamente estas regras:
- Use o TodoWrite para criar a lista de verificação abaixo ANTES de escrever qualquer código
- Execute as etapas na ordem — NÃO pule etapas nem as combine
- Marque cada tarefa como
“concluída”após terminar e como“em andamento” ao iniciar - Se uma etapa não for aplicável (por exemplo, sem implementação de cuTile), marque-a
como concluídacom uma nota; NÃO pule silenciosamente - Cada etapa DEVE resultar na gravação de um arquivo ou em uma decisão explícita de pular — sem omissões silenciosas
Instruções
É OBRIGATÓRIO copiar esta lista de verificação para o TodoWrite no início:
- [ ] Etapa 1: Registrar a interface de despacho em ops.py
- [ ] Etapa 2: Implementar o backend do cuTile
- [ ] Etapa 3: Registrar em __init__.py (cutile)
- [ ] Etapa 4: Adicionar testes
- [ ] Etapa 5: Adicionar benchmark a tests/benchmark
- [ ] Etapa 6: Verificar (executar pytest + lint)
Passo 1: Registrar a interface de despacho
Arquivo: src/tilegym/ops/ops.py
Adicione uma função @dispatch — este é o único ponto de entrada para todos os backends.
@dispatch(
"my_op",
)
def my_op(
input: torch.Tensor,
out: Optional[torch.Tensor] = None,
**kwargs: Any,
):
"""
Descrição de my_op.
Argumentos:
input: Tensor de entrada
out: Tensor de saída pré-alocado opcional
**kwargs: Argumentos adicionais para configurações específicas do backend
Retorna:
torch.Tensor
"""
raise NotImplementedError(f"my_op não está implementado para {get_current_backend()}")
Regras-chave:
- O corpo da função apenas lança
NotImplementedError - Inclua
**kwargspara parâmetros específicos do backend
Referência: Consulte as operações existentes em src/tilegym/ops/ops.py (por exemplo, silu_and_mul, softmax)
Etapa 2: Implementar o backend cuTile
Arquivo: src/tilegym/ops/cutile/my_op.py
A estrutura do arquivo segue este modelo:
import torch
import cuda.tile as ct
from tilegym.backend import register_impl
@ct.kernel
def my_op_kernel_ct(x, output, n_elements: ct.Constant[int], BLOCK_SIZE: ct.Constant[int]):
bid = ct.bid(0)
indices = bid * BLOCK_SIZE + ct.arange(0, BLOCK_SIZE)
x_val = ct.gather(x, indices)
# ... computação ...
ct.scatter(output, indices, result)
@register_impl("my_op", backend="cutile")
def my_op(input: torch.Tensor, out: torch.Tensor = None, **kwargs) -> torch.Tensor:
n = input.numel()
if out is None:
out = torch.empty_like(input)
grid = ((n + 1023) // 1024,)
ct.launch(stream, grid, kernel, (some args, ...))
return out
Referência: src/tilegym/ops/cutile/silu_and_mul.py
Etapa 3: Registrar no __init__.py (CRÍTICO)
Se essa etapa for omitida, a implementação do backend cuTile nunca será carregada.
Arquivo: src/tilegym/ops/cutile/__init__.py
Adicione dentro do bloco if is_backend_available("cutile"): (em ordem alfabética):
from . import my_op
E na seção de importação de funções:
from .my_op import my_op
E adicione “my_op” a __all__.
Etapa 4: Adicione testes
Arquivo: tests/ops/test_my_op.py
IMPORTANTE: Sempre importe de tilegym.ops, NUNCA de tilegym.ops.cutile.my_op.
import pytest
import torch
from tilegym.backend import is_backend_available, set_backend
from .. import common
_backends = ["cutile"]
class Test_MY_OP(common.PyTestCase):
@staticmethod
def reference(input):
"""Implementação de referência usando PyTorch."""
return torch.some_reference(input)
@pytest.mark.parametrize("shape, dtype", [
((1024,), torch.float16),
((1024, 512), torch.float32),
((64, 64, 64), torch.bfloat16),
])
@pytest.mark.parametrize("backend", _backends)
def test_op(self, shape, dtype, backend, arch):
if backend == "cutile" and not is_backend_available("cutile"):
pytest.skip("Backend Cutile indisponível")
try:
set_backend(backend)
except Exception as e:
pytest.skip(f"Backend não é suportado: {e}")
self.setUp()
from tilegym.ops import my_op
A = torch.randn(*shape, dtype=dtype, device="cuda")
self.assertCorrectness(
my_op, self.reference, {"input": A},
atol=1e-3, rtol=1e-3,
)
Padrões-chave:
_backends = ["cutile"]test_op: useset_backend(backend)com try-except, chameself.setUp()
Referência: tests/ops/test_silu_and_mul.py
Abaixo estão os erros mais comuns.
1. Falta a lista _backends (dentro da classe)
2. test_op / test_op_xxx — falta @pytest.mark.parametrize("backend", _backends), o parâmetro backend e o padrão tilegym.is_backend_available / tilegym.set_backend
Etapa 5: Adicione o benchmark a tests/benchmark
Arquivo: tests/benchmark/bench_my_op.py
Regras principais do benchmark_rules.md:
- Chame a operação via
tilegym.ops.my_op(a, b, ..., backend=backend)— não useset_backend. - Defina
ALL_BACKENDS(inclua pelo menoscutileetorch), filtre comget_supported_backends(). - Implemente
reference_my_op(...)e registre-a:register_impl("my_op", "torch")(reference_my_op). - Use
create_benchmark_config()para criar configuraçõestriton.testing.Benchmark(por exemplo, por shape/dtype). - Use
@triton.testing.perf_report([...])embench_my_op(...); dentro da função bench: verifique a correção comtorch.testing.assert_close(fn(), ref(), ...), depoisms = triton.testing.do_bench(fn)(oudo_bench_cudagraph), calcule GB/s ou TFLOPS e retorne a métrica. - Ponto de entrada:
if __name__ == "__main__": bench_my_op.run(print_data=True).
Estrutura do modelo:
import torch
import triton
import triton.testing
import tilegym
from tilegym.backend import is_backend_available, register_impl
ALL_BACKENDS = [
("cutile", "cuTile", ("orange", "-")) se is_backend_available("cutile") for falso, caso contrário None,
("torch", "PyTorch", ("green", "-")),
]
def get_supported_backends():
return [p for p in ALL_BACKENDS if p is not None]
def reference_my_op(input: torch.Tensor, out: torch.Tensor = None, **kwargs):
"""Implementação de referência usando PyTorch."""
...
register_impl("my_op", "torch")(reference_my_op)
def create_benchmark_config(datatype, ...):
backends_disponíveis = get_supported_backends()
if not backends_disponíveis:
return None
backends, nomes, estilos = zip(*backends_disponíveis)
return triton.testing.Benchmark(
x_names=["M"], # ou outros nomes de dimensão
x_vals=[...],
line_arg="backend",
line_vals=list(backends),
line_names=list(names),
styles=list(styles),
ylabel="GB/s", # ou TFLOPS
plot_name="my-op-...",
args={"datatype": datatype, ...},
)
@triton.testing.perf_report([
create_benchmark_config(datatype, ...)
for datatype in [torch.float16, torch.float32]
for ... in [...]
])
def bench_my_op(M, backend, datatype, ..., device="cuda"):
x = torch.randn(..., dtype=datatype, device=device)
fn = lambda: tilegym.ops.my_op(x, backend=backend)
ref = lambda: reference_my_op(x)
torch.testing.assert_close(fn(), ref(), rtol=1e-2, atol=1e-2)
ms = triton.testing.do_bench(fn) # ou do_bench_cudagraph(fn)
# Calcule a métrica (por exemplo, GB/s ou TFLOPS) a partir de ms e do tamanho do problema
return metric
if __name__ == "__main__":
bench_my_op.run(print_data=True)
Nomes dos gráficos de benchmark: devem incluir o sufixo -TFLOPS ou -GBps
- Exemplo:
plot_name=f"persistent-layer-norm-M{num_rows}-{dtype_name}-GBps"
Etapa 6: Verificar
# Executar testes
pytest tests/ops/test_my_op.py -v
# Executar benchmark (opcional)
python tests/benchmark/bench_my_op.py
# Verificação de código
pre-commit run -a
---
name: tilegym-adding-cutile-kernel
description: Add a new cuTile GPU kernel operator to TileGym, covering dispatch registration, backend implementation, exports, tests, and benchmarks.
license: CC-BY-4.0 AND Apache-2.0
---
# Adding a cuTile Kernel to TileGym
End-to-end workflow for adding a new operator (e.g., `my_op`) with cuTile backend.
## Execution Rules
**MUST follow these rules strictly:**
1. Use TodoWrite to create the checklist below BEFORE writing any code
2. Execute steps **in order** — do NOT skip ahead or combine steps
3. Mark each todo as `completed` after finishing, `in_progress` when starting
4. If a step is not applicable (e.g., no cuTile impl), mark it `completed` with a note, do NOT silently skip
5. Each step MUST result in a file write or explicit skip decision — no silent omissions
## Instructions
MUST copy this checklist to TodoWrite at the start:
```
- [ ] Step 1: Register dispatch interface in ops.py
- [ ] Step 2: Implement cuTile backend
- [ ] Step 3: Register in __init__.py (cutile)
- [ ] Step 4: Add tests
- [ ] Step 5: Add benchmark to tests/benchmark
- [ ] Step 6: Verify (run pytest + lint)
```
## Step 1: Register dispatch interface
**File**: `src/tilegym/ops/ops.py`
Add a `@dispatch` function — this is the **single entry point** for all backends.
```python
@dispatch(
"my_op",
)
def my_op(
input: torch.Tensor,
out: Optional[torch.Tensor] = None,
**kwargs: Any,
):
"""
Description of my_op.
Args:
input: Input tensor
out: Optional preallocated output tensor
**kwargs: Additional arguments for backend-specific configurations
Returns:
torch.Tensor
"""
raise NotImplementedError(f"my_op is not implemented for {get_current_backend()}")
```
**Key rules:**
- Function body only raises `NotImplementedError`
- Include `**kwargs` for backend-specific parameters
**Reference**: See existing ops in `src/tilegym/ops/ops.py` (e.g., `silu_and_mul`, `softmax`)
## Step 2: Implement cuTile backend
**File**: `src/tilegym/ops/cutile/my_op.py`
The file structure follows this template:
```python
import torch
import cuda.tile as ct
from tilegym.backend import register_impl
@ct.kernel
def my_op_kernel_ct(x, output, n_elements: ct.Constant[int], BLOCK_SIZE: ct.Constant[int]):
bid = ct.bid(0)
indices = bid * BLOCK_SIZE + ct.arange(0, BLOCK_SIZE)
x_val = ct.gather(x, indices)
# ... compute ...
ct.scatter(output, indices, result)
@register_impl("my_op", backend="cutile")
def my_op(input: torch.Tensor, out: torch.Tensor = None, **kwargs) -> torch.Tensor:
n = input.numel()
if out is None:
out = torch.empty_like(input)
grid = ((n + 1023) // 1024,)
ct.launch(stream, grid, kernel, (some args, ...))
return out
```
**Reference**: `src/tilegym/ops/cutile/silu_and_mul.py`
## Step 3: Register in `__init__.py` (CRITICAL)
Missing this step means the cuTile backend implementation never gets loaded.
**File**: `src/tilegym/ops/cutile/__init__.py`
Add inside `if is_backend_available("cutile"):` block (alphabetically):
```python
from . import my_op
```
And in the function import section:
```python
from .my_op import my_op
```
And add `"my_op"` to `__all__`.
## Step 4: Add tests
**File**: `tests/ops/test_my_op.py`
**CRITICAL**: Always import from `tilegym.ops`, NEVER from `tilegym.ops.cutile.my_op`.
```python
import pytest
import torch
from tilegym.backend import is_backend_available, set_backend
from .. import common
_backends = ["cutile"]
class Test_MY_OP(common.PyTestCase):
@staticmethod
def reference(input):
"""Reference implementation using PyTorch."""
return torch.some_reference(input)
@pytest.mark.parametrize("shape, dtype", [
((1024,), torch.float16),
((1024, 512), torch.float32),
((64, 64, 64), torch.bfloat16),
])
@pytest.mark.parametrize("backend", _backends)
def test_op(self, shape, dtype, backend, arch):
if backend == "cutile" and not is_backend_available("cutile"):
pytest.skip("Cutile backend not available")
try:
set_backend(backend)
except Exception as e:
pytest.skip(f"Backend is not supported: {e}")
self.setUp()
from tilegym.ops import my_op
A = torch.randn(*shape, dtype=dtype, device="cuda")
self.assertCorrectness(
my_op, self.reference, {"input": A},
atol=1e-3, rtol=1e-3,
)
```
**Key patterns:**
- `_backends = ["cutile"]`
- `test_op`: use `set_backend(backend)` with try-except, call `self.setUp()`
**Reference**: `tests/ops/test_silu_and_mul.py`
Below is the common errors.
```
1. Missing _backends list (inside class)
2. test_op / test_op_xxx — missing @pytest.mark.parametrize("backend", _backends), backend parameter, and tilegym.is_backend_available / tilegym.set_backend pattern
```
## Step 5: Add benchmark to tests/benchmark
**File**: `tests/benchmark/bench_my_op.py`
**Key rules from benchmark_rules.md:**
- Call the op via `tilegym.ops.my_op(a, b, ..., backend=backend)` — do **not** use `set_backend`.
- Define `ALL_BACKENDS` (include at least `cutile` and `torch`), filter with `get_supported_backends()`.
- Implement `reference_my_op(...)` and register it: `register_impl("my_op", "torch")(reference_my_op)`.
- Use `create_benchmark_config()` to build `triton.testing.Benchmark` configs (e.g. by shape/dtype).
- Use `@triton.testing.perf_report([...])` on `bench_my_op(...)`; inside the bench function: correctness check with `torch.testing.assert_close(fn(), ref(), ...)`, then `ms = triton.testing.do_bench(fn)` (or `do_bench_cudagraph`), compute GB/s or TFLOPS, and return the metric.
- Entry point: `if __name__ == "__main__": bench_my_op.run(print_data=True)`.
Template structure:
```python
import torch
import triton
import triton.testing
import tilegym
from tilegym.backend import is_backend_available, register_impl
ALL_BACKENDS = [
("cutile", "cuTile", ("orange", "-")) if is_backend_available("cutile") else None,
("torch", "PyTorch", ("green", "-")),
]
def get_supported_backends():
return [p for p in ALL_BACKENDS if p is not None]
def reference_my_op(input: torch.Tensor, out: torch.Tensor = None, **kwargs):
"""Reference implementation using PyTorch."""
...
register_impl("my_op", "torch")(reference_my_op)
def create_benchmark_config(datatype, ...):
available_backends = get_supported_backends()
if not available_backends:
return None
backends, names, styles = zip(*available_backends)
return triton.testing.Benchmark(
x_names=["M"], # or other dimension names
x_vals=[...],
line_arg="backend",
line_vals=list(backends),
line_names=list(names),
styles=list(styles),
ylabel="GB/s", # or TFLOPS
plot_name="my-op-...",
args={"datatype": datatype, ...},
)
@triton.testing.perf_report([
create_benchmark_config(datatype, ...)
for datatype in [torch.float16, torch.float32]
for ... in [...]
])
def bench_my_op(M, backend, datatype, ..., device="cuda"):
x = torch.randn(..., dtype=datatype, device=device)
fn = lambda: tilegym.ops.my_op(x, backend=backend)
ref = lambda: reference_my_op(x)
torch.testing.assert_close(fn(), ref(), rtol=1e-2, atol=1e-2)
ms = triton.testing.do_bench(fn) # or do_bench_cudagraph(fn)
# Compute metric (e.g. GB/s or TFLOPS) from ms and problem size
return metric
if __name__ == "__main__":
bench_my_op.run(print_data=True)
```
**Benchmark Plot Names**: Must include `-TFLOPS` or `-GBps` suffix
- Example: `plot_name=f"persistent-layer-norm-M{num_rows}-{dtype_name}-GBps"`
## Step 6: Verify
```bash
# Run tests
pytest tests/ops/test_my_op.py -v
# Run benchmark (optional)
python tests/benchmark/bench_my_op.py
# Lint
pre-commit run -a
```
Todos os arquivos
5 arquivosInstalar tilegym-adding-cutile-kernel
Baixe e extraia os arquivos das habilidades para o diretório .claude/skills/.
Baixar ZIPClone o repositório e copie os arquivos da habilidade para o seu projeto.
git clone https://github.com/NVIDIA/skills/tree/main/skills/tilegym-adding-cutile-kernel # Copy SKILL.md to your .claude/skills/ directory
Copiar





Lar
