4 ms·

That has got to be a total drop in the bucket compared the cost of the syscall itself.

• valarauca1 8y ago
  Kernel interrupt handling is incredibly quick. Tasking switching an the related MMU updates is slower. As you have to perform a kernel interrupt handling action just to start initializing the task switch.
  • majewsky 8y ago
    Interrupt handling is quick, paging isn't.
    • monocasa 8y ago
      The KPTI Meltdown fixes mean that interrupt handling _is_ paging on a lot of chips out there.
  • amluto 8y ago
    Careful. x86 interrupt handling is slow. System calls use an accelerated mechanism that is much faster.
• deleted 8y ago
  [deleted]
• gameswithgo 8y ago
  drops add up
  • taeric 8y ago
    Not when they are 1:1 with what you are talking about, do they? I mean, I get that across the lifetime of an application, you might see that 1% of your cost is in this somehow, but then the easier response would almost certainly be to do less syscalls, since if this is taking up 1% then the syscalls are taking up 10%+? (And that is assuming this is 10% of the syscall. Ish)