On 05/05/2011 03:32 PM, Andi Kleen wrote:
From: Andi Kleen<ak@xxxxxxxxxxxxxxx> We found that the changes to take anon vma root chain lock lead to excessive lock contention on a fork intensive workload on a 4S system. Use the new batch lock infrastructure to optimize the fork() path, where it is very common to acquire always the same lock. This patch does not really lower the contention, but batches the lock taking/freeing to lower the bouncing overhead when multiple forks are working at the same time. Essentially each user will get more work done inside a locking region. Reported-by: Tim Chen<tim.c.chen@xxxxxxxxxxxxxxx> Cc: Andrea Arcangeli<aarcange@xxxxxxxxxx> Cc: Rik van Riel<riel@xxxxxxxxxx> Signed-off-by: Andi Kleen<ak@xxxxxxxxxxxxxxx>
Reviewed-by: Rik van Riel<riel@xxxxxxxxxx> -- All rights reversed -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>