linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: paul.szabo@sydney.edu.au
Cc: 695182@bugs.debian.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Reproducible OOM with just a few sleeps
Date: Mon, 14 Jan 2013 16:56:15 -0800	[thread overview]
Message-ID: <50F4A92F.2070204@linux.vnet.ibm.com> (raw)
In-Reply-To: <201301142036.r0EKaYGN005907@como.maths.usyd.edu.au>

On 01/14/2013 12:36 PM, paul.szabo@sydney.edu.au wrote:
> I understand that more RAM leaves less lowmem. What is unacceptable is
> that PAE crashes or freezes with OOM: it should gracefully handle the
> issue. Noting that (for a machine with 4GB or under) PAE fails where the
> HIGHMEM4G kernel succeeds and survives.

You have found a delta, but you're not really making apples-to-apples
comparisons.  The page tables (a huge consumer of lowmem in your bug
reports) have much more overhead on a PAE kernel.  A process with a
single page faulted in with PAE will take at least 4 pagetable pages
(it's 7 in practice for me with sleeps).  It's 2 pages minimum (and in
practice with sleeps) on HIGHMEM4G.

There's probably a bug here.  But, it's incredibly unlikely to be seen
in practice on anything resembling a modern system.  The 'sleep' issue
is easily worked around by upgrading to a 64-bit kernel, or using sane
ulimit values.  Raising the vm.min_free_kbytes sysctl (to perhaps 10x of
its current value on your system) is likely to help the hangs too,
although it will further "consume" lowmem.

I appreciate your persistence here, but for a bug with such a specific
use case, and with so many reasonable workarounds, it's not something I
want to dig in to much deeper.  I'll be happy to answer any questions if
you want to go digging deeper, or want some pointers on where to go
looking to fix this properly.

--
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>

  parent reply	other threads:[~2013-01-15  1:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  3:31 [RFC] Reproducible OOM with just a few sleeps paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36   ` paul.szabo
2013-01-15  0:34     ` Bug#695182: " Ben Hutchings
2013-01-15  0:56     ` Dave Hansen [this message]
2013-01-15  2:16       ` paul.szabo
2013-01-30 12:51       ` Pavel Machek
2013-01-30 15:32         ` Dave Hansen
2013-01-30 19:40           ` paul.szabo
2013-01-31  5:15             ` Bug#695182: " Ben Hutchings
2013-01-31  9:07               ` paul.szabo
2013-01-31 13:38                 ` Ben Hutchings
2013-01-31 23:06                   ` paul.szabo
2013-02-01  1:07                     ` Ben Hutchings
2013-02-01  2:12                       ` paul.szabo
2013-02-01  2:57                         ` Ben Hutchings
2013-02-01  3:13                           ` paul.szabo
2013-02-01  4:38                             ` Phil Turmel
2013-02-01 10:20                               ` Pavel Machek
2013-02-01 10:25                                 ` PAE problems was " Pavel Machek
2013-02-01 16:57                                   ` H. Peter Anvin
2013-02-01 17:45                                     ` Ben Hutchings
2013-02-07  0:28                                   ` Dave Hansen
2013-02-10 19:09                                     ` Pavel Machek
2013-02-17  9:10   ` Simon Jeons
2013-02-24 22:10     ` paul.szabo
  -- strict thread matches above, loose matches on Subject: below --
2013-01-12 19:41 paul.szabo
2013-01-15 10:25 Sedat Dilek
2013-01-17 21:04 paul.szabo
2013-01-17 21:55 ` Dave Hansen

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=50F4A92F.2070204@linux.vnet.ibm.com \
    --to=dave@linux.vnet.ibm.com \
    --cc=695182@bugs.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paul.szabo@sydney.edu.au \
    /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).