News for hackers. Stuff that matters.
Re:Practical Libc-free threading on Linux by jart on Friday March 24, 2023 @01:35AM (#35285433)
Explain how to do locks without using the lock instruction!
Re:Practical Libc-free threading on Linux by jnordwick on Friday March 24, 2023 @06:19AM (#35287162)
does xchg count
Re:Practical Libc-free threading on Linux by jart on Friday March 24, 2023 @02:01PM (#35293108)
That's an implicit lock.
Re:Practical Libc-free threading on Linux by monocasa on Friday March 24, 2023 @10:15AM (#35289341)
futex will do lock instructions for you in kernel space. It's non optimal to just jump to kernel space every time, but it should still at least be correct.
Re:Practical Libc-free threading on Linux by jart on Friday March 24, 2023 @02:02PM (#35293114)
A system call has even more overhead than the lock prefix!
Re:Practical Libc-free threading on Linux by monocasa on Friday March 24, 2023 @02:34PM (#35293544)
True, but arguably this article constrains itself to the kernel-user boundary, where atomic instructions could be considered out of scope considering how the Linux syscall ABI is constructed.
Re:Practical Libc-free threading on Linux by jart on Saturday March 25, 2023 @06:48AM (#35301374)