FFPA self attention; layout follows SDPA: (B, H, N, D).

August 21, 2026 · View on GitHub

Fast and Memory-Efficient Exact Attention for Large Headdim


FFPA: Fast and Memory-Efficient Exact Attention for Large Headdim, achieving O(1) SRAM complexity (w/ Split-D) and O(d/4) register complexity, 1.5x~15x speedup over PyTorch SDPA. FFPA extends the headdim support beyond D > 256 (up to 1024) without any precision loss.

Self AttnGQA/MQACross AttnCausal/MaskDropoutHeaddimFwd/Bwd
✔️(Nq=Nkv)✔️(Hq!=Hkv)✔️(Nq!=Nkv)✔️(attn_mask)✔️(p>0)320~10241.5x~15x↑

Latest News

  • [2026-08] 🐍 Cache-DiT x FFPA (FP8/FP4) is ready! Feel free to take a try for your Diffusion models. 🎉🎉
  • [2026-08] 🚪 FFPA now experimental supports FP4 Attention for headdims [64,1024] (sm_120, forward only), achieving 850-980🎉 TFLOPS (D=128-256) on NVIDIA RTX 5090, 3.8x~4.4x🎉 speedup over PyTorch SDPA (FlashAttention-2 backend), the performance of large headdims is stay tuned for updates. 🎉🎉
  • [2026-08] 🦅 FFPA now supports D=512 for NVIDIA B200 via CuTe-DSL tcgen05 2-CTA, 1517 TFLOPS forward and 763 TFLOPS backward, achieving 6x~15x🎉 speedup over standard PyTorch SDPA. 🎉🎉
  • [2026-07] 🎯 FFPA now supports FP8 Attention for headdims [64,1024] (sm_120, forward only) and achieving 3x~6x🎉 speedup over PyTorch SDPA for large headdim (D>256). 🎉🎉
  • [2026-06] FFPA now supports AMD ROCm/HIP GPUs via the TritonBackend, check #268 for more details. 🎉
  • [2026-06] 🦅 NVIDIA-Nemo/AutoModel x FFPA achieving 1.4x~1.5x🎉 End2End training throughput speedup for Gemma4-31B (8xH200, FSDP2 + AC) with FFPA accelerating the 10/60 (D=512) full-attention layers. 🎉🎉
  • [2026-06] 🐍 FFPA now supports TritonBackend and CuTeDSLBacked for both forward and backward pass, achieving 1.5x~5x🎉 speedup over standard PyTorch SDPA across many devices. 🎉🎉
  • [2026-05] 🚪 FFPA now supports GQA, MQA, cross-attn, causal, attn-mask and dropout with CUDABackend for large headdims (D>256, forward only), achieving 1.3x~2x🎉 speedup over PyTorch SDPA. 🎉🎉

Quick Start

First, install the prebuilt package from PyPI or build ffpa-attn from source:

# First, install the prebuilt package from PyPI
pip3 install -U ffpa-attn # CUDA 13.0+, PyTorch 2.11+
# Or, build ffpa-attn from source, just follow the cmds
git clone https://github.com/xlite-dev/ffpa-attn.git
# Then, build the wheel package (Triton + CuTe-DSL backends)
cd ffpa-attn && pip3 install -e . --no-build-isolation
# Optional: install ffpa-attn w/ CUDA backend (forward only)
# ext all: build all kernels, include fp8/fp4 attention kernels
bash ./build.sh --arch sm_120f --ext all --headdim all

Then, try to accelerate the attention for large headdim with just one-line of code:

>>> import torch.nn.functional as F
>>> from ffpa_attn import ffpa_attn_func
>>> # Monkey-patch SDPA to point to FFPA. Every thing that FFPA
>>> # does not support will auto fallback to SDPA: N < 512, etc.
>>> F.scaled_dot_product_attention = ffpa_attn_func

Or, try the minimal BF16 usage example — Self-Attention (B=1, H=32, N=8192, D=512):

import torch
import torch.nn.functional as F
from ffpa_attn import ffpa_attn_func

# D: 64, 128, ..., 320, ..., 1024 (FA-2 <= 256, FFPA supports up to 1024).
B, H, N, D = 1, 32, 8192, 512 # batch_size, num_heads, seq_len, head_dim
q = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")
k = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")
v = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")

# FFPA self attention; layout follows SDPA: (B, H, N, D).
out = ffpa_attn_func(q, k, v)  # -> torch.Tensor of shape (B, H, N, D)
ref = F.scaled_dot_product_attention(q, k, v)

print(f"FFPA vs SDPA max_abs_err={(out - ref).abs().max().item():.4e}")

Or, try the minimal FP8/FP4 usage example with CUDABackend (sm_120, forward only):

import torch
import torch.nn.functional as F
from ffpa_attn import CUDABackend, ffpa_attn_func
from functools import partial

# D: 64, 128, ..., 320, ..., 1024 (FA-2 <= 256, FFPA supports up to 1024).
B, H, N, D = 1, 32, 8192, 128 # batch_size, num_heads, seq_len, head_dim
q = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")
k = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")
v = torch.randn(B, H, N, D, dtype=torch.bfloat16, device="cuda")

# Currenly, fp8/fp4 attention are only supported on sm_120, forward only.
fp8_backend = CUDABackend(backward=False, forward=True, enable_fp8=True)
fp4_backend = CUDABackend(backward=False, forward=True, enable_fp4=True)
ffpa_attn_func_fp8 = partial(ffpa_attn_func, forward_backend=fp8_backend)
ffpa_attn_func_fp4 = partial(ffpa_attn_func, forward_backend=fp4_backend)

# FFPA self attention; layout follows SDPA: (B, H, N, D).
out_fp8 = ffpa_attn_func_fp8(q, k, v)  # -> torch.Tensor of shape (B, H, N, D)
out_fp4 = ffpa_attn_func_fp4(q, k, v)  # -> torch.Tensor of shape (B, H, N, D)
ref = F.scaled_dot_product_attention(q, k, v)

print(f"FFPA FP8 vs SDPA max_abs_err={(out_fp8 - ref).abs().max().item():.4e}")
print(f"FFPA FP4 vs SDPA max_abs_err={(out_fp4 - ref).abs().max().item():.4e}")

For more advanced features, please refer to our online docs at 📘ffpa-attn.io.

Split-D and TiledMMA

We extend FlashAttention to support large headdim (D>256D>256) via fine-grained tiling at the MMA level for QKQK^\top and PVPV matrix multiplication. Two orthogonal O(D)O(D) bottlenecks — SRAM footprint and register pressure — are broken by Split-D and TiledMMA<4,2,1> respectively.

Split-D: The tiling of the DD axis breaks the SRAM bottleneck. A persist-D layout keeps QQ resident in SRAM at O(D)O(D) (D=512192KB>99KBD{=}512 \Rightarrow 192\text{KB} > 99\text{KB} per-CTA limit on sm_8x/sm_120). Split-D chunks the DD axis, keeping SRAM fixed at Br×16B_r \times 16 (with Br=BcB_r=B_c) for Q, K and V, yielding constant SRAM complexity O(Br×16)O(1)O(B_r \times 16) \approx O(1).

TiledMMA: The M4N2 layout breaks the register bottleneck. The QKQK^\top has N=BcN{=}B_c (fixed, independent of DD), so its acc is O(1)O(1); the PVPV GEMM instead has N=DN{=}D, so the OO acc costs D/(2Nw)D/(2{\cdot}N_w) regs/thread. M8N1 (FA-2 style, Nw=1N_w{=}1) O(D/2)\Rightarrow O(D/2): at D=512D{=}512 this already reaches 256 regs/thread, over the 255 architectural limit and spilling. Splitting NN to M4N2 (FA-1 style, Nw=2N_w{=}2) halves it to O(D/4)O(D/4), keeping D=1024D{=}1024 just feasible (256 regs/thread).

Dispatch: M8N1 for D512D \le 512, M4N2 for D>512D > 512. On RTX 5090, M4N2 delivers 1.55× the throughput of M8N1 at D=1024D{=}1024 (154T vs 100T, where M8N1 collapses from register spilling).

Benchmark

Runnable benchmark are provided under bench. The performance benchmarks for the NVIDIA L20 (Ada), NVIDIA Geforce RTX 5090 (Blackwell), NVIDIA H800 PCIE (Hopper), NVIDIA H200 SXM (Hopper, CuTe-DSL backend, up to 535 TFLOPS!), B200 (Blackwell, CuTe-DSL tcgen05 2-CTA D=512 backend, up to 1517 TFLOPS forward and 763 TFLOPS backward!) with large headdims can be found at bench.


BF16 Attention for Large Headdim: FFPA vs SDPA (FWD/BWD) across NVIDIA H200 and B200, 6x-15x↑.


FP8 Attention for Large/Small Headdim: FFPA vs SDPA (FWD) on NVIDIA RTX 5090, 3x-6x↑.


FP4 Attention for Large/Small Headdim: FFPA vs SDPA (FWD) on NVIDIA RTX 5090, 4x-7x↑.

Backends

FFPA supports multiple backends for the forward and backward pass, including: SDPA (baseline), CUDA (forward only), Triton, and CuTe-DSL. The CuTe-DSL backend is currently in early stage, stay tuned for future updates. The Triton backend (forward + backward) also runs on AMD GPUs.

BackendArchFwdBwdHeaddimAutotuneSpeedupRecommend
SDPAsm>=75All✖️1.0xsm>=75
CUDAsm>=80✖️320~1024✖️1.5x~3xsm_80~89,120{a,f}
CUDA FP8sm_120{a,f}✖️64~1024✖️3x~6xsm_120{a,f}
CUDA FP4sm_120{a,f}✖️64~512✖️4x~7xsm_120{a,f}
Tritonsm>=80320~10241.5x~5xsm>=80
CuTe-DSLsm>=80320~1024✖️1.5x~2xsm_80~89,120{a,f}
CuTe-DSLsm_90a320~512✖️3x~6xsm_90a
CuTe-DSLsm_100a512✖️6x~15xsm_100a

How to use different backends for your own scenario? Users can simply pass the Backend configs (SDPABackend, CUDABackend, TritonBackend or CuTeDSLBackend) to ffpa_attn_func, for example:

>>> from ffpa_attn import ffpa_attn_func, CuTeDSLBackend
>>> # CuTe-DSL backend, D=512 scenario, fastest on H200!
>>> o = ffpa_attn_func(q, k, v, backend=CuTeDSLBackend())

Persistent Autotune

Generate device-specific tuned configs for production deployment (currently, Triton only), avoiding per-process autotune cost. The generated JSON is saved under configs dir and automatically loaded when runtime autotune is disabled (the default). See the docs of Triton Autotune for details.

python -m ffpa_attn.autotune --mode max --full-tasks --overwrite # 1 GPU
export CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7 # Multi-GPU (`pip install ray`)
python -m ffpa_attn.autotune --mode max --full-tasks --num-gpus 8 --overwrite

End-to-End Training

NVIDIA-NeMo Automodel PR #2436 shows that on Gemma4-31B training (L=8192, 8xH200, FSDP2 + Activation Checkpointing), accelerating the 10/60 (D=512) full-attention layers with FFPA delivers about 1.4x~1.5x higher throughput (E2E) than SDPA at similar memory footprint, with loss aligned within normal bf16 noise.

End-to-End Inference

The FFPA (FP8/FP4) attention has fully integrated into Cache-DiT. Currently, the FP8/FP4 attention supports most of the attention headdims range from 64 to 1024 (forward only), including any headdims that can be divided by 8, covering self-attention, cross-attention, causal attention and GQA/MQA attention. Feel free to take a try for your Diffusion models. For examples: (FLUX.1-dev, seed=42, 28 steps)

python3 -m cache_dit.generate flux --attn native   --seed 42 --height 1024 --width 1024
python3 -m cache_dit.generate flux --attn ffpa_fp8 --seed 42 --height 1024 --width 1024
python3 -m cache_dit.generate flux --attn ffpa_fp4 --seed 42 --height 1024 --width 1024

FLUX.1-dev, seed=42, 28 steps, 1024 x 1024, NVIDIA RTX PRO 5000

SDPA-FA2 (17.2s)FFPA-FP8 (16.6s)SageAttn-3 (FP4, 16.4s)FFPA-FP4 (16.4s)

FLUX.1-dev, seed=42, 28 steps, 2048 x 2048, NVIDIA RTX PRO 5000

SDPA-FA2 (92.3s)FFPA-FP8 (83.5s)SageAttn-3 (FP4, 80.4s)FFPA-FP4 (78.4s)

The performance and precision of FFPA (FP8/FP4) is still under active development, stay tuned for future updates. Please note that the FP8/FP4 attention is not suitable for all scenarios (e.g., small models or short seqlen), and we recommend users to evaluate the precision and performance of FFPA (FP8/FP4) for their own use cases.

License

Apache License 2.0

Citations

@misc{deftruth2026ffpa,
  author       = {DefTruth and Butterfingrz},
  title        = {FFPA: Fast and Memory-Efficient Exact Attention for Large Headdim},
  year         = {2026},
  publisher    = {Zenodo},
  version      = {v1.0},
  doi          = {10.5281/zenodo.20638547},
  url          = {https://doi.org/10.5281/zenodo.20638547}
}

References