public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cameron Schaus <cam@schaus.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.20 OOM with 8Gb RAM
Date: Thu, 12 Apr 2007 15:30:18 -0600	[thread overview]
Message-ID: <461EA4EA.2020208@schaus.ca> (raw)
In-Reply-To: <20070412121553.c7fd3249.akpm@linux-foundation.org>

Andrew Morton wrote:
> All of ZONE_NORMAL got used by ramdisk, and networking wants to
> allocate a page from ZONE_NORMAL.  An oom-killing is the correct
> response, although probably not effective.
>
> ramdisk is a nasty thing - cannot you use ramfs or tmpfs?
>   
Sure enough, changing the ramdisk to a tmpfs did the trick.  No more OOM 
(at least for now).

Thanks!
Cam



  reply	other threads:[~2007-04-12 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 17:38 2.6.20 OOM with 8Gb RAM Cameron Schaus
2007-04-12 19:15 ` Andrew Morton
2007-04-12 21:30   ` Cameron Schaus [this message]
2007-04-13 22:39   ` Jason Lunz
2007-04-13 22:46     ` Andrew Morton
2007-04-13 22:54       ` William Lee Irwin III
2007-04-13 23:32         ` Andrew Morton
2007-04-13 23:40           ` William Lee Irwin III
2007-04-13 23:01       ` Jason Lunz

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=461EA4EA.2020208@schaus.ca \
    --to=cam@schaus.ca \
    --cc=akpm@linux-foundation.org \
    --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