> The problem, as I see it, is that you can dirty pages 10-15 times
> faster than they can be written to disk. So, you will always
> have the possibility of an OOM situation as long as you are I/O
> bound.
That's not a problem at all. I think the VM never starts
pageout IO on a page that doesn't look like it'll become
freeable after the IO is done, so we simply shouldn't go
into the OOM killer as long as there are pages waiting on
pageout IO to finish.
Once we really are OOM we shouldn't have pages in pageout
IO.
This is what I am doing in current 2.4-rmap and it seems
to do the right thing in both the "heavy IO" and the "out
of memory" corner cases.
-- Great minds drink alike.- 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/