fork semantically copies all of a process’s memory, so without overcommit a process that’s using more than half of available memory can’t fork, which means that the fork/exec combo to spawn new processes doesn’t work.
-
-
- 6 more replies
New conversation -
-
-
We should all just adopt posix_spawn instead :3
-
I think posix_spawn is just a libc wrapper around fork/exec
- 1 more reply
New conversation -
-
-
Not to mention the TLB shootdowns and page faults caused by using fork/exec to spawn subprocesses
-
(Which vfork successfully mitigates, but vfork is not a solution anybody should be happy about)
End of conversation
New conversation -
-
-
Why not both?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We can just turn it off, start using vfork, and stop using the software that breaks. Great chance to rewrite that crufty C program in Rust or Zig :-)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
True, but I think it has more recent and useful use cases nowdays
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
