Fpstate Vso - ^hot^

Traditionally, the kernel could assume a fixed size for the floating-point state. However, modern x86 architectures use , where the amount of data saved during a context switch depends on which CPU features (like AVX, AVX-512, or AMX) the application actually uses.

The transition to a variable state object model was a major rework for the Linux kernel to support high-performance computing needs: fpstate vso

This refers to the dynamically sized nature of the floating-point state buffer. Because a task using AMX (Advanced Matrix Extensions) requires much more memory to save its state than a task only using SSE, the kernel uses VSOs to allocate only what is necessary. Traditionally, the kernel could assume a fixed size