On Mon, 9 Jul 2001, Mike Galbraith wrote:
>> But still this may be a hint. You are not running out of swap,
>> aren't you?
>
> I'm running oom whether I have swap enabled or not. The inactive
> dirty list starts growing forever, until it's full of (aparantly)
> dirty pages and I'm utterly oom.
>
> With swap enabled, I keep allocating until there's nothing left.
> Actual space usage is roughly 30mb (of 256mb), but when you can't
> allocate anymore you're toast too, with the same dirt buildup.
AFAIU you are running oom without the oom killer kicking in.
That's reasonable with tmpfs: the tmpfs pages are accounted to the
page cache, but are not freeable if there is no free swap space. So
the vm tries to free memory without success. (The same should be true
for ramfs but exaggerated by the fact that ramfs can never free the
page)
In the -ac series I introduced separate accounting for shmem pages and
do reduce the page cache size by this count for meminfo and
vm_enough_memory. Perhaps the oom coding needs also some knowledge
about this?
Greetings
Christoph
-
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/