On Tue, Mar 29, 2011 at 09:32:06PM -0400, Sean Noonan wrote: > > Ok, so that looks like root cause of the problem. can you try the > > patch below to see if it fixes the problem (without any other > > patches applied or reverted). > > It looks like this does fix the deadlock problem. However, it > appears to come at the price of significantly higher mmap startup > costs. It shouldn't make any difference to startup costs with the current code uses read faults to populate the region and that doesn't cause any allocation to occur and hence this code is not executed during the populate phase. Is this repeatable or is it just a one-off result? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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>