Messages in this thread | ![/](/images/icornerl.gif) | | Date | Tue, 21 Jul 2009 13:03:18 -0700 | Subject | Re: [PATCH] copy over oom_adj value at fork time | From | Paul Menage <> |
| |
On Tue, Jul 21, 2009 at 1:00 PM, David Rientjes<rientjes@google.com> wrote: > 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? >
It's the API that's existed for years with no complaints, AFAICS.
Paul
| ![\](/images/icornerr.gif) |