Messages in this thread Patch in this message | | | Subject | [patch] scheduler: rebalance_tick interval update | From | Darren Hart <> | Date | Mon, 15 Nov 2004 14:38:33 -0800 |
| |
The current rebalance_tick() code assigns each sched_domain's last_balance field to += interval after performing a load_balance. If interval is 10, this has the effect of saying: we want to run load_balance at time = 10, 20, 30, 40, etc... If for example last_balance=10 and for some reason rebalance_tick can't be run until 30, load_balance will be called and last_balance will be updated to 20, causing it to call load_balance again immediately the next time it is called since the interval is 10 and we are already at >30. It seems to me that it would make much more sense for last_balance to be assigned jiffies after a load_balance, then the meaning of last_balance is more exact: "this domain was last balanced at jiffies" rather than "we last handled the balance we were supposed to do at 20, at some indeterminate time". The following patch makes this change.
Signed-off-by: Darren Hart <dvhltc@us.ibm.com> ---
diff -purN -X /home/mbligh/.diff.exclude /home/linux/views/linux-2.6.10-rc1-mm5/kernel/sched.c linux-2.6.10-rc1-mm5-jni/kernel/sched.c --- /home/linux/views/linux-2.6.10-rc1-mm5/kernel/sched.c 2004-11-11 05:33:53.000000000 -0800 +++ linux-2.6.10-rc1-mm5-jni/kernel/sched.c 2004-11-15 11:28:16.000000000 -0800 @@ -2201,7 +2201,7 @@ static void rebalance_tick(int this_cpu, /* We've pulled tasks over so no longer idle */ idle = NOT_IDLE; } - sd->last_balance += interval; + sd->last_balance = jiffies; } } }
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |