In __oom_kill_task(), there is a comment that says,
"We give our sacrificial lamb high priority and access to all the memory it needs. That way it should be able to exit() and clear out its resources quickly..."
However, we don't actually change the priority at that point, we just give it a large timeslice.
Would it make sense to actually change the priority/policy using sched_setscheduler() to give the process a deeply negative nice level or maybe even make it realtime?
This seems to help on some of our OOM stress tests. Chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
