Hi, I have here a very specific workload that I want to test in Linux without the "child-runs-first and in the parent's processor" behaviour. I know that this behaviour is very good for general workloads because of the cache affinity; but in my specific case I want that a short-lived fork()ed process starts to run immediately after the fork(), in the other CPU. I've modified sched.c:wake_up_new_task() in order to prevent the scheduler to run the child first [it was easy, even for a newbie like me :-)], but I'm not sure about how to make the child run in the other processor. Can anyone help me? Thanks, Daniel -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/