linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: paul.szabo@sydney.edu.au, 695182@bugs.debian.org
Cc: dave@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: Bug#695182: [RFC] Reproducible OOM with just a few sleeps
Date: Tue, 15 Jan 2013 00:34:33 +0000	[thread overview]
Message-ID: <1358210073.15692.60.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <201301142036.r0EKaYGN005907@como.maths.usyd.edu.au>

[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]

On Tue, 2013-01-15 at 07:36 +1100, paul.szabo@sydney.edu.au wrote:
> Dear Dave,
> 
> >> Seems that any i386 PAE machine will go OOM just by running a few
> >> processes. To reproduce:
> >>   sh -c 'n=0; while [ $n -lt 19999 ]; do sleep 600 & ((n=n+1)); done'
> >> ...
> > I think what you're seeing here is that, as the amount of total memory
> > increases, the amount of lowmem available _decreases_ due to inflation
> > of mem_map[] (and a few other more minor things).  The number of sleeps
> > you can do is bound by the number of processes, as you noticed from
> > ulimit.  Creating processes that don't use much memory eats a relatively
> > large amount of low memory.
> > This is a sad (and counterintuitive) fact: more RAM actually *CREATES*
> > RAM bottlenecks on 32-bit systems.
> 
> 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.
[...]

Sorry, let me know where to send your refund.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-01-15  0:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12  3:31 paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36   ` paul.szabo
2013-01-15  0:34     ` Ben Hutchings [this message]
2013-01-15  0:56     ` Dave Hansen
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

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=1358210073.15692.60.camel@deadeye.wl.decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=695182@bugs.debian.org \
    --cc=dave@linux.vnet.ibm.com \
    --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