From: Andrea Arcangeli <andrea@suse.de>
To: Peter Zaitsev <peter@mysql.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: VM Problems in 2.6.7 (Too active OOM Killer)
Date: Thu, 15 Jul 2004 02:04:38 +0200 [thread overview]
Message-ID: <20040715000438.GS974@dualathlon.random> (raw)
In-Reply-To: <1089848823.15336.3895.camel@abyss.home>
On Wed, Jul 14, 2004 at 04:47:04PM -0700, Peter Zaitsev wrote:
> To be honest I do not really understand this OOM without swap problem at
> all, why is it possible to move pages from ZONE_NORMAL to swap but not
> to other zones ?
the oom without swap you reproduced is not related to ZONE_NORMAL
shortage. The pages in ZONE_NORMAL never goes into swap.
the ZONE_NORMAL oom is a separate issue from the oom killing you
reproduced. with 2.6.7 if you were hitting the ZONE_NORMAL shortage your
machine would lockup and it would never oom-kill anything (Andrew just
changed that in kernel CVS, so thanks to that change a ZONE_NORMAL
shortage will not deadlock anymore in 2.6.8, but OTOH in 2.6.8 adding
swap will not be enough anymore to workaround the oom-killing you
reproduced).
About the ZONE_NORMAL shortage without swap, rather than running
cpu-cache-hungry memcopies from lowmemzone to highmem (or even worse to
pass through swap like it happens in 2.6 mainline with swap enabled), I
believe it's better to reserve some ram in the lowmem zone, 800M of ram
on a 32G box should be a cheap price to pay compared to the cpu/IO cost
involved in moving memory around during the bench.
next prev parent reply other threads:[~2004-07-15 0:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 2:23 VM Problems in 2.6.7 (Too active OOM Killer) Peter Zaitsev
2004-07-14 2:40 ` William Lee Irwin III
2004-07-14 3:20 ` Peter Zaitsev
2004-07-14 3:17 ` Andrea Arcangeli
2004-07-14 3:44 ` Peter Zaitsev
2004-07-14 4:10 ` Andrea Arcangeli
2004-07-14 4:22 ` Andrew Morton
2004-07-14 4:47 ` Andrea Arcangeli
2004-07-14 4:17 ` Andrew Morton
2004-07-14 23:47 ` Peter Zaitsev
2004-07-14 22:44 ` Andrew Morton
2004-07-15 0:06 ` Andrea Arcangeli
2004-07-15 0:30 ` Peter Zaitsev
2004-07-15 0:46 ` Andrea Arcangeli
2004-07-15 1:54 ` William Lee Irwin III
2004-07-15 2:13 ` Peter Zaitsev
2004-07-15 2:33 ` William Lee Irwin III
2004-07-15 2:39 ` William Lee Irwin III
2004-07-15 2:44 ` William Lee Irwin III
2004-08-13 22:23 ` William Lee Irwin III
2004-07-19 20:27 ` Bill Davidsen
2004-07-18 16:13 ` Kurt Garloff
2004-07-20 9:14 ` R. J. Wysocki
2004-07-20 13:29 ` Andrea Arcangeli
2004-07-20 13:53 ` William Lee Irwin III
2004-07-20 13:29 ` William Lee Irwin III
2004-07-19 20:21 ` Bill Davidsen
2004-07-15 0:04 ` Andrea Arcangeli [this message]
2004-07-15 0:43 ` Peter Zaitsev
2004-07-15 0:43 ` William Lee Irwin III
2004-07-15 1:04 ` Peter Zaitsev
2004-07-15 1:29 ` William Lee Irwin III
2004-07-14 3:50 ` William Lee Irwin III
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=20040715000438.GS974@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@mysql.com \
/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