Hugging Face's logo

Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
Back to feed
danieldk 
posted an update 1 day ago
Post
67
We have recently added Torch Stable ABI support to kernels and kernel-builder. This allows kernel developers to target a particular Torch version and the kernel will be supported on that Torch version and later Torch versions (up to ~2 years).

This makes it much easier to write kernels with long-term support and not just the last two Torch releases.

We have also started rolling out Stable ABI support to kernels in kernels-community, starting with Flash Attention 3, supporting Torch 2.9 and later as well as CUDA versions starting at 12.6:

https://huggingface.co/kernels/kernels-community/flash-attn3/tree/v1/build
dipankarsarkar

Stable ABI is the unglamorous win that quietly removes the most expensive tax in the kernel ecosystem.

Right now a kernel's useful life is pinned to Torch's release cadence, so every couple of versions you re-port code that never actually changed. Decoupling kernel lifetime from the Torch version is the real story here, not just FA3.

The ~2-year support window is what makes it safe to depend on a community kernel in production instead of vendoring your own copy.

Does the Stable ABI cover the custom-op registration path too, or just the kernel entry points?
In this post