Prev: [patch 0/3] x86: Use interval tree to keep track of PAT reserve/free
Next: [tip:x86/irq] x86: Avoid race condition in pci_enable_msix()
From: David Rientjes on 23 Feb 2010 03:20
On Tue, 23 Feb 2010, Balbir Singh wrote:

> > The oom killer presently kills current whenever there is no more memory
> > free or reclaimable on its mempolicy's nodes. There is no guarantee that
> > current is a memory-hogging task or that killing it will free any
> > substantial amount of memory, however.
> >
> > In such situations, it is better to scan the tasklist for nodes that are
> > allowed to allocate on current's set of nodes and kill the task with the
> > highest badness() score. This ensures that the most memory-hogging task,
> > or the one configured by the user with /proc/pid/oom_adj, is always
> > selected in such scenarios.
> >
> > Signed-off-by: David Rientjes <rientjes(a)google.com>
>
> Seems reasonable, but I think it will require lots of testing.

I already tested it by checking that tasks with very elevated oom_adj
values don't get killed when they do not share the same MPOL_BIND nodes as
a memory-hogging task.

What additional testing did you have in mind?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: [patch 0/3] x86: Use interval tree to keep track of PAT reserve/free
Next: [tip:x86/irq] x86: Avoid race condition in pci_enable_msix()