On Tue, 3 Aug 2010 16:21:11 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote: > On Tue, 3 Aug 2010 00:23:32 -0700 (PDT) > David Rientjes <rientjes@xxxxxxxxxx> wrote: > > > > Especially with memcg, it just shows a _broken_ value. > > > > > > > Not at all, the user knows what tasks are attached to the memcg and can > > easily determine which task is going to be killed when it ooms: simply > > iterate through the memcg tasklist, check /proc/pid/oom_score, and sort. > > > > And finds > at system oom, process A is killed. > at memcg oom, process B is killed. > > funny non-deteministic interace, aha. > I said - you have beutiful legs. (new logic of oom calculation) - but your face is ugly (new oom_score_adj) then - I bought a mask for you (oom_disable for memcg.) Then, please don't use your time for convince me your face is beutiful. It's waste of time. Thanks, -Kame -- 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>