From: Peter Zaitsev <peter@mysql.com>
To: Andrew Morton <akpm@osdl.org>
Cc: andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: VM Problems in 2.6.7 (Too active OOM Killer)
Date: Wed, 14 Jul 2004 17:30:52 -0700 [thread overview]
Message-ID: <1089851451.15336.3962.camel@abyss.home> (raw)
In-Reply-To: <20040714154427.14234822.akpm@osdl.org>
On Wed, 2004-07-14 at 15:44, Andrew Morton 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 ?
>
> If the kernel has no swap there is nothing it can do with an anonymous page
> (ie: the thing whcih malloc() gives you). It is effectively pinned memory,
> because there's nowhere we can write it to get rid of it.
Why can't it be moved to other zone if there is a lot of place where ?
In general I was not pushing system in some kind of stress mode - There
was still a lot of cache memory available. Why it could not be instead
shrunk to accommodate allocation ?
As I understand in my case with 4G there is Normal zone and HighMem
zone where "user" anonymous memory can be located in any of these zones.
Is this observation correct ?
>
> If you end up pinning all of your ZONE_NORMAL pages with anonymous memory,
> further GFP_KERNEL allocation attempts will go oom.
Aha I see. So user level memory allocations can't cause OOM only kernel
level allocations can ? In this case why do not you have some reserved
amount of space for these types of allocations by default ?
In this case I also do not understand how swap space helps here ? If you
can't move page to over zone or shrink cache because of allocation type
how it happens you can however perform page swap ?
--
Peter Zaitsev, Senior Support Engineer
MySQL AB, www.mysql.com
next prev parent reply other threads:[~2004-07-15 1:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 2:23 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 [this message]
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
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=1089851451.15336.3962.camel@abyss.home \
--to=peter@mysql.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®