3 ms·
The kernel has changed its threading APIs, the clone API, and how syscalls are made several times in the past, and you cannot predict how they will change in fu
by userbinator 4y ago
The kernel has changed its threading APIs, the clone API, and how syscalls are made several times in the past, and you cannot predict how they will change in future.
I thought "don't break userspace" was one of the key principles of Linux design?
- rwmj 4y agoThe old APIs continue to be supported, but they may be slower or have other limitations. eg You can continue to make syscalls through int $0x80 if you want, even on the latest x86, but performance will suck. You can keep using clone instead of clone3, but you won't get to use all the newer features.
- vanviegen 4y agoSo your code will keep on working as good as it ever did. I fail to see the problem with that.
- pedrocr 4y agoNothing guarantees that. clone() may still be provided by the kernel but nothing guarantees it will still be fast and not just a compatibility retrofit. Particularly since most users will move on automatically through libc.