Re:Spectre mitigations murder userspace performance
by dsp on Saturday June 19, 2021 @07:44PM
(#27565620)
> having the kernel execute consecutive systemcalls without switching the context
io_uring enables exactly this
Re:Spectre mitigations murder userspace performance
by emilfihlman on Sunday June 20, 2021 @09:13AM
(#27569622)
Only for io, which is not the same thing.
Re:Spectre mitigations murder userspace performance
by dsp on Sunday June 20, 2021 @12:47PM
(#27571743)
Despite the name, there is nothing io-specific about the io_uring interface. Non-io syscalls can be added. Io syscalls just tend to benefit the most (due to call frequency).
Re:Spectre mitigations murder userspace performance
by quotemstr on Saturday June 19, 2021 @07:38PM
(#27565576)
> Syscall chaining refers to having the kernel execute consecutive systemcalls without switching the context back to userspace.
io_uring already gives you that. You can submit multiple operations in a batch and link the operations together so that if one operation in a chain of linked operations fails, io_uring won't try to execute the rest.
Re:Spectre mitigations murder userspace performance
by emilfihlman on Sunday June 20, 2021 @09:13AM
(#27569621)
Which is not syscall chaining, but message chaining, of io.
Syscall chaining refers to having the kernel execute consecutive systemcalls without switching the context back to userspace.
An example of this might be closing a multitude of file descriptors or registering signals or writing the same data to multiple fds etc, which becomes prohibitely expensive if you need to do it multiple times quickly, and actually doing it even once is really expensive if your sets are large.