diff options
| author | Peter Zijlstra <a.p.zijlstra@chello.nl> | 2009-11-27 17:32:46 +0100 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2009-12-09 10:03:05 +0100 |
| commit | cd29fe6f2637cc2ccbda5ac65f5332d6bf5fa3c6 (patch) | |
| tree | b4206012d424a8c0bce1f260d042c678db0602a2 /kernel/latencytop.c | |
| parent | ab19cb23313733c55e0517607844b86720b35f5f (diff) | |
| download | blackbird-op-linux-cd29fe6f2637cc2ccbda5ac65f5332d6bf5fa3c6.tar.gz blackbird-op-linux-cd29fe6f2637cc2ccbda5ac65f5332d6bf5fa3c6.zip | |
sched: Sanitize fork() handling
Currently we try to do task placement in wake_up_new_task() after we do
the load-balance pass in sched_fork(). This yields complicated semantics
in that we have to deal with tasks on different RQs and the
set_task_cpu() calls in copy_process() and sched_fork()
Rename ->task_new() to ->task_fork() and call it from sched_fork()
before the balancing, this gives the policy a clear point to place the
task.
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions
