The news. On July 8, 2026, a study (arXiv:2607.07706) analyzed post-hoc transformer linearization in a frozen-backbone setting across LLaMA and Qwen models up to 32B parameters. It argues softmax attention relies on key-dependent, rank-1 orthogonal projections, then adds structural interventions — sink tokens, short convolutions, and fixed-budget cache routing — that improve long-context behavior without retraining the base model, reportedly matching the long-context retrieval of far more complex adaptive-caching frameworks. The point is not a new model but a recipe: the same frozen weights keep their training and are handed cheap structural add-ons instead of being retrained. Read the paper →
Training-free linear attention takes a model that was trained with ordinary softmax attention and converts it to a cheaper, fixed-memory form, with the original weights left frozen. Picture a reference librarian who has always answered questions by walking into an endless archive and pulling any book she needs — for every question, from anywhere in the stacks. That is softmax attention: exact, but the archive she has to search keeps growing with every book added. Now the budget is cut and she is handed one small cart with a fixed number of shelves. She is the same librarian with the same training — nobody re-taught her — she simply has to work from the cart. On her own, she would forget most of the archive. Training-free linear attention is the trick of keeping the same librarian and the same training, but handing her one fixed-size cart plus a few tricks, so she rarely misses the book she actually needs.
Underneath the metaphor, the growing archive is the KV cache. Ordinary softmax attention stores a Key and a Value for every token, so the memory it must scan grows linearly with context length — the deeper into a long document you go, the more it costs. Linear attention swaps that growing archive for a single fixed-size state — constant memory no matter how long the context — but a plain swap on an already-trained model loses the sharp, far-back lookups softmax was doing. The paper frames softmax attention as leaning on key-dependent, rank-1 selections that a plain linear map struggles to reproduce, which is why a naive conversion tends to forget. How you update that fixed state matters too — the study weighs a delta rule (write and erase entries explicitly) against gated accumulation (decay the old, add the new) as the state-update backbone.
So instead of retraining, the study bolts three cheap fixes onto the frozen model, and each maps to something the cart was missing. Sink tokens, a short convolution, and fixed-budget cache routing add back exactly the pieces the linear state drops — a few always-kept anchors, the local detail, and a rule for which tokens earn a slot in the bounded cache. Sink tokens are the reference books bolted to the cart so the earliest context never washes out; the short convolution is the sticky note of the last page or two, restoring short-range precision; and fixed-budget cache routing is the rule that decides which of the many past tokens get to occupy the cart's limited shelves — the piece the paper isolates as the one that actually recovers long-context retrieval. That routing decision is the same family of choice a serving engine makes when it evicts from a bounded cache:
Remove earliest tokens first
Where it earns its keep
Take a 32B model at a 32,768-token context (illustrative numbers — the paper reports models up to 32B and long-context retrieval matching adaptive-caching frameworks, not these exact counts). With full softmax attention, the model keeps a Key and Value for every one of the 32,768 tokens, and that cache grows without bound as the conversation gets longer. Now fix the cache budget at 2,048 slots and hand the model the three add-ons. The question is no longer "store everything" but "which 2,048 of the 32,768 tokens earn a slot?" — sink tokens claim the first few, the short convolution covers the last few, and fixed-budget cache routing spends the rest of the budget on the tokens it keeps. 32,768 tokens, but still only 2,048 cache slots — a ~16× smaller cache, held constant as the context grows instead of growing with it. That is the kind of trade the frozen-backbone recipe is built to make — the base model itself is never retrained.
| Route to linear attention | Retrains the model? | Long-context memory | Long-context recall |
|---|---|---|---|
| Full softmax attention (baseline) | no — it is the original | grows with context (KV cache) | strong, but increasingly expensive |
| Distill / retrain into a linear or hybrid form (e.g. Taylor-Calibrate) | yes — training or distillation tokens | fixed-size state | recoverable, but needs a training budget |
| Training-free linearization + fixed-budget cache routing | no — the backbone stays frozen | fixed-budget cache (~bounded slots) | matches adaptive-caching frameworks, per the paper (setup-dependent, illustrative) |
Because the change lives in how attention reads its history rather than in the model's weights, it should in principle stack with the rest of the long-context toolkit — a smarter eviction rule, a different state update, or grouped-query sharing of the cache are all orthogonal to it — and the real-world gain will depend on the model family and how much long-range recall the task demands. The headline is not a new architecture; it is a recipe for making an existing trained model attend linearly at long context without retraining the base model — with fixed-budget cache routing doing the heavy lifting.
Goes deeper in: LLM Internals → Attention → Computing Attention Scores
Continue in trackKV Cache — why softmax attention's memory grows, and what a fixed budget buysRelated explainers
- Taylor-Calibrate — Taylor-guided gate initialization — the distillation route to linear attention; this study instead keeps the backbone frozen and adds structure on top
- Gated DeltaNet 2 — decoupled erase/write gates — the delta-rule vs gated state update this paper weighs, built into an architecture from the start
- WorldKV — evict then reinsert the KV cache — another take on the fixed-budget question: which past tokens deserve a cache slot
- Baidu Unlimited OCR — constant KV via reference sliding window — holding the cache constant over long inputs by a different structural trick