On Wed, 28 Oct 2015, Hongjie Fang (方洪杰) wrote: > Under a userspace perspective, get a different value than he wrote, > it must be confusing. >
It's confusing, but with purpose: it shows there is no direct mapping between /proc/pid/oom_adj and /proc/pid/oom_score_adj. /proc/pid/oom_score_adj is the effective policy and has been for years. The value returned by /proc/pid/oom_adj demonstrates reality vs what is perceived and is a side-effect of integer division truncating the result in C. It's a bad situation, I agree, and we anticipated the complete removal of /proc/pid/oom_adj years ago since it has been deprecated for years. Maybe one day we can convince Linus that is possible, but until then we're stuck with it.
