lkml.org 
[lkml]   [2010]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Revert oom rewrite series
On Mon, 15 Nov 2010, Alan Cox wrote:

> > The goal was to make the oom killer heuristic as predictable as possible
> > and to kill the most memory-hogging task to avoid having to recall it and
> > needlessly kill several tasks.
>
> Meta question - why is that a good thing. In a desktop environment it's
> frequently wrong, in a server environment it is often wrong. We had this
> before where people spend months fiddling with the vm and make it work
> slightly differently and it suits their workload, then other workloads go
> downhill. Then the cycle repeats.
>

Most of the arbitrary heuristics were removed from oom_badness(), things
like nice level, runtime, CAP_SYS_RESOURCE, etc., so that we only consider
the rss and swap usage of each application in comparison to each other
when deciding which task to kill. We give root tasks a 3% bonus since
they tend to be more important to the productivity or uptime of the
machine, which did exist -- albeit with a more dramatic impact -- in the
old heursitic.

You'll find that the new heuristic always kills the task consuming the
most amount of rss unless influenced by userspace via the tunables (or
within 3% of root tasks).

We always want to kill the most memory-hogging task because it avoids
needlessly killing additional tasks when we must immediately recall the
oom killer because we continue to allocate memory. If that task happens
to be of vital importance to userspace, then the user has full control
over tuning the oom killer priorities in such circumstances.

> > You have full control over disabling a task from being considered with
> > oom_score_adj just like you did with oom_adj. Since oom_adj is
> > deprecated for two years, you can even use the old interface until then.
>
> Which changeset added it to the Documentation directory as deprecated ?
>

51b1bd2a was the actual change that deprecated it, which was a direct
follow-up to a63d83f4 which actually obsoleted it.


\
 
 \ /
  Last update: 2010-11-15 21:59    [W:0.061 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site