I had to implement fork on the first Posix implementation, under CTOS back in the 90's?
It is a terrible thing. Inefficient doesn't begin to cover it. Duplicating an entire process state, page tables and code bindings and allocations and on and on. What does the child do next? Usually, it exec()s which means "exit and run this other thing).
Literally double the overhead that you wanted.
spawn() is probably what most people should do, instead of fork().
It is a terrible thing. Inefficient doesn't begin to cover it. Duplicating an entire process state, page tables and code bindings and allocations and on and on. What does the child do next? Usually, it exec()s which means "exit and run this other thing).
Literally double the overhead that you wanted.
spawn() is probably what most people should do, instead of fork().
reply