3 ms·
When the address isn't in the process page table accessing it traps into the kernel; then you've got to do all the cache clearing stuff for speculative executio
by toast0 3y ago
When the address isn't in the process page table accessing it traps into the kernel; then you've got to do all the cache clearing stuff for speculative execution vulnerabilities; then the paging logic needs to figure out what to do, in this case because of the set limit, you've also got to demote at least one page, which means updating the page table, but also sending IPIs to all processors to flush that page/those pages from the TLBs; and then you return to execution.
If you're accessing a lot of pages, mostly randomly, it's going to be a mess. If you're decompressing files (as an installer might do), and the compression window is large relative to the limit (as it might be to get the highest compression ratio), that could be a lot of mostly random access to pages, causing a lot of page faults, and high cpu.
- ComputerGuru 3y agoAlso context switching between kernel and user mode is now heavier than ever courtesy of speculative execution mitigations.