2 ms·
Getting a new syscall on linux is hard. You'll often need user-space users before it gets accepted; that alone is hard. The linux syscall set is very small cons
by marcodiego 6y ago
Getting a new syscall on linux is hard. You'll often need user-space users before it gets accepted; that alone is hard. The linux syscall set is very small considered the breadth of cases it is used today. Compared to nt, linux syscall set is very small and well thought out.
- formerly_proven 6y agoWindows has around 500 syscalls, Linux around 300. Both have several escape-hatches for arbitrary driver-userspace communication, which makes the number of syscalls pretty irrelevant. (E.g. Linux has ioctl, netlink, procfs, sysfs, ...)
- Ericson2314 6y ago> Both have several escape-hatches for arbitrary driver-userspace communication, which makes the number of syscalls pretty irrelevant. (E.g. Linux has ioctl, netlink, procfs, sysfs, ...) Yes, we need a better metric for accounting for those things, which will paint a much more sobering picture of the complexity and growth of complexity of the userland <-> kernel interface.
- monocasa 6y agoWell, there's also win32k.sys which provides an additional 1000 or so syscalls.
- marcodiego 6y agoCompare this: https://linuxhint.com/list_of_linux_syscalls/ https://linuxhint.com/list_of_linux_syscalls/ with https://j00ru.vexillium.org/syscalls/nt/64/ https://j00ru.vexillium.org/syscalls/nt/64/ and https://j00ru.vexillium.org/syscalls/win32k/64/ https://j00ru.vexillium.org/syscalls/win32k/64/
- GoblinSlayer 6y agoLinux syscall set is very small and posix. No matter what you think, the first version is always a prototype.