public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Lunz <lunz@falooley.org>
Cc: Cameron Schaus <cam@schaus.ca>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.20 OOM with 8Gb RAM
Date: Fri, 13 Apr 2007 15:46:53 -0700	[thread overview]
Message-ID: <20070413154653.21fdb914.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070413223935.GA6783@metaxa.reflex>

On Fri, 13 Apr 2007 18:39:36 -0400
Jason Lunz <lunz@falooley.org> wrote:

> On Thu, Apr 12, 2007 at 12:15:53PM -0700, 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?
> 
> What do you mean by "nasty thing"?

It's just weird - it exploits internal knowledge of VFS behaviour, diddles
with pagecache within a fake disk strategy handler, etc.

Furthermore, because it pretends to be a block device, the VFS will not use
highmem pages when accessing the ramdisk.  So the 8GB machine will go splat
with only 800MB of ramdisk.

ramfs is much cleaner and does not have that limitation.

> I've heard that about loopback too.

loopback does some pretty weird thigns too, but it has more of an excuse:
it is a specialised layering thing, whereas ramdisk is, umm, just a
ramdisk.

> If I want to run a system entirely from ram with a compressed filesystem
> image mounted on /, is it better to store that image in a ramdisk, or on
> a tmpfs and mount it via loopback?

Store it all in ramfs, no loopback needed?

  reply	other threads:[~2007-04-13 22:46 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
2007-04-13 22:39   ` Jason Lunz
2007-04-13 22:46     ` Andrew Morton [this message]
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=20070413154653.21fdb914.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cam@schaus.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunz@falooley.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