> Followup to: <Pine.LNX.4.33L.0108102347050.3530-100000@imladris.rielhome.conectiva>
> By author: Rik van Riel <riel@conectiva.com.br>
> In newsgroup: linux.dev.kernel
> >
> > I haven't got the faintest idea how to come up with an OOM
> > killer which does the right thing for everybody.
>
> Basically because there is no such thing?
And also because
- people mix OOM and thrashing handling up - when they are logically
seperated questions.
- The 2.4 VM goes completely gaga under high load. Its beautiful under
light loads, there nobody can touch it, but when you actually really
need it - splat.
So people either need to get an OOM when they are not but in fact might
thrash, or the box thrashes so hard it makes insufficient progress to
actually get out of memory.
OOM is also very hard to get right without reservations tracking in kernel
for the journalling file systems and other similar stuff. To an extent
thrash handling also wants RSS limits.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 15 2001 - 21:00:38 EST