GPU bank conflicts can slow reads 32x: why vLLM deliberately scrambles memory
anbarth · x · 2026-11-16
A bank conflict can make a GPU shared-memory read take 32 passes where 1 would do — and correctness tests never catch it. The author illustrates the mechanics (32 banks, one 4-byte value per pass per bank) and explains swizzling, the trick vLLM kernels use to deliberately store data scrambled and avoid conflicts.
Related event: vLLM Uses Swizzling to Eliminate GPU Shared Memory Bank Conflicts(3 posts)→
More from Infra
- Profiling bank conflicts with Nsight Compute: a hands-on guide — anbarth · 2026-11-16
- GPU bank conflicts can slow reads 32x: why vLLM deliberately scrambles memory — anbarth · 2026-11-16
- Sentry CEO: Durable Objects complexity is Cloudflare platform's biggest weakness — zeeg · 2026-11-16
- WSJ: Nvidia's days as the AI economy's open checkbook are numbered — Gregory_C_Allen · 2026-11-16
- Survey maps how LLMs now deploy on edge devices via software optimization and hardware — kalyan_kpl · 2026-11-16
- SemiAnalysis layer-by-layer teardown reveals how Kirin 9050 implements LogicFolding — teortaxesTex · 2026-11-16