3 ms·
So, the answer is “we don’t think we need three, let alone four, but we happen to have two bad ones that we don’t want to get rid of”? If those old ones don’t
by Someone 8y ago
So, the answer is “we don’t think we need three, let alone four, but we happen to have two bad ones that we don’t want to get rid of”?
If those old ones don’t have any unique properties, couldn’t they be implemented on top of a single syscall, or is the syscall interface sacred on Linux, and calls cannot be retired?
- LukeShu 8y agoThe syscall interface is considered to be Linux's public API, and must very strictly never break backward compatibility. They cannot retire syscalls.
- caf 8y agoWhat tends to happen is that kernel is changed to implement the old syscall using the new infrastructure on the kernel side. There's no real cost to having another syscall number used.
- Someone 8y agoBut it grows the amount of code in the kernel, making it more likely to be buggy, more so if some of these old interfaces get used less and less (and, hence, likely tested less and less), and the underlying root interface gets refactored again and again to support new polling interfaces.
- caf 8y agoWe are generally talking about very simple wrapper functions here that don't have a lot of scope for hidden bugs to creep in.