Re:The lost malloc()
by 0c3ca83 on Wednesday November 04, 2026 @09:44AM
(#50366230)
There's no syscall on every allocation.
[ Parent
| on HN ]
That's why I put the word "potential" in there. Every allocation potentially needs to go to the OS for more pages.
And every memory access potentially enters the kernel via a page fault.
Any given CPU instruction potentially isn't in cache.
And yet, they can't all not be in cache. As soon as the cache is accessed for one instruction, a bunch more are pulled in too.
Any given vector.push call could reallocate the vector, but it's amortized O(1).