From: Vlastimil Babka <vbabka@suse.cz>
To: John Moser <john.r.moser@gmail.com>
Cc: linux-kernel@vger.kernel.org, "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: OOM at low page cache?
Date: Tue, 27 Jan 2015 12:03:34 +0100 [thread overview]
Message-ID: <54C77086.7090505@suse.cz> (raw)
In-Reply-To: <54C2C89C.8080002@gmail.com>
CC linux-mm in case somebody has a good answer but missed this in lkml traffic
On 01/23/2015 11:18 PM, John Moser wrote:
> Why is there no tunable to OOM at low page cache?
>
> I have no swap configured. I have 16GB RAM. If Chrome or Gimp or some
> other stupid program goes off the deep end and eats up my RAM, I hit
> some 15.5GB or 15.75GB usage and stay there for about 40 minutes. Every
> time the program tries to do something to eat more RAM, it cranks disk
> hard; the disk starts thrashing, the mouse pointer stops moving, and
> nothing goes on. It's like swapping like crazy, except you're reading
> library files instead of paged anonymous RAM.
>
> If only I could tell the system to OOM kill at 512MB or 1GB or 95%
> non-evictable RAM, it would recover on its own. As-is, I need to wait
> or trigger the OOM killer by sysrq.
>
> Am I just the only person in the world who's ever had that problem? Or
> is it a matter of questions fast popping up when you try to do this
> *and* enable paging to disk? (In my experience, that's a matter of too
> much swap space: if you have 16GB RAM and your computer dies at 15.25GB
> usage, your swap space should be no larger than 750MB plus inactive
> working RAM; obviously, your computer can't handle paging 750MB back and
> forth. If you make it 8GB wide and you start swap thrashing at 2GB
> usage, you have too much swap available).
>
> I guess you could try to detect excessive swap and page cache thrashing,
> but that's complex; if anyone really wanted to do that, it would be done
> by now. A low-barrier OOM is much simpler.
> --
> 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/
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2015-01-27 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54C2C89C.8080002@gmail.com>
2015-01-27 11:03 ` Vlastimil Babka [this message]
2015-01-28 6:26 ` OOM at low page cache? Minchan Kim
2015-01-28 12:36 ` Rik van Riel
2015-01-28 14:13 ` John Moser
2015-01-28 14:15 ` John Moser
2015-01-29 1:24 ` Minchan Kim
2015-01-28 14:27 ` John Moser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C77086.7090505@suse.cz \
--to=vbabka@suse.cz \
--cc=john.r.moser@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).