Messages in this thread | | | Date | Tue, 21 Jul 2009 13:00:19 -0700 (PDT) | From | David Rientjes <> | Subject | Re: [PATCH] copy over oom_adj value at fork time |
| |
On Tue, 21 Jul 2009, Paul Menage wrote:
> Agreed, but the same livelock can be fixed in ways that don't break > the API. (E.g. check for the victim being OOM_DISABLED in > select_bad_process() when we find a new "worst" candidate). >
And allow /proc/pid-of-child/oom_score to represent a possible candidate (and, additionally, a hint at the oom killing priority) when it really isn't?
| |