On Tue, 2003-02-11 at 17:10, Arador wrote: > in 2.5 Documentation/sched-design.txt: > > - run fork()ed children before the parent. Andrea has pointed out the > advantages of this a few months ago, but patches for this feature > do not work with the old scheduler as well as they should, > because idle processes often steal the new child before the fork()ing > CPU gets to execute it. > > > The question is what advantages has, to run the fork()ed children > before their parents?;) (I can't imagine any...) 1) Assuming the child will do very little before an exec, if the parent runs first, then it'll probably cause a lot more COW faults 2) In many cases, then parent may just wait for the child to do something (think of a shell running a command). So it doesn't make much sense for the parent to execute first so it can go to sleep. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
