On Sun, 6 Jun 2010 15:34:35 -0700 (PDT) David Rientjes <rientjes@xxxxxxxxxx> wrote: > The oom killer tasklist dump, enabled with the oom_dump_tasks sysctl, is > very helpful information in diagnosing why a user's task has been killed. > It emits useful information such as each eligible thread's memory usage > that can determine why the system is oom, so it should be enabled by > default. Unclear. On a large system the poor thing will now spend half an hour squirting junk out the diagnostic port. Probably interspersed with the occasional whine from the softlockup detector. And for many applications, spending a long time stuck in the kernel printing diagnostics is equivalent to an outage. I guess people can turn it off again if this happens, but they'll get justifiably grumpy at us. I wonder if this change is too developer-friendly and insufficiently operator-friendly. -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>