All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	linux-mm@kvack.org, akpm@zip.com.au, hugh@veritas.com,
	linux-kernel@vger.kernel.org
Subject: Re: dbench on tmpfs OOM's
Date: Mon, 16 Sep 2002 22:14:03 -0700	[thread overview]
Message-ID: <3D86BA1B.84873680@digeo.com> (raw)
In-Reply-To: 210772234.1032213704@[10.10.2.3]

"Martin J. Bligh" wrote:
> 
> >> ...
> >> MemTotal:     32107256 kB
> >> MemFree:      27564648 kB
> >
> > I'd be suspecting that your node fallback is bust.
> >
> > Suggest you add a call to show_free_areas() somewhere; consider
> > exposing the full per-zone status via /proc with a proper patch.
> 
> Won't /proc/meminfo.numa show that? Or do you mean something
> else by "full per-zone status"?

meminfo.what?   Remember when I suggested that you put
a testing mode into the numa code so that mortals could
run numa builds on non-numa boxes?


> Looks to me like it's just out of low memory:
> 
> > LowFree:          1424 kB
> 
> There is no low memory on anything but node 0 ...
> 

It was a GFP_HIGH allocation - just pagecache.

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	linux-mm@kvack.org, akpm@zip.com.au, hugh@veritas.com,
	linux-kernel@vger.kernel.org
Subject: Re: dbench on tmpfs OOM's
Date: Mon, 16 Sep 2002 22:14:03 -0700	[thread overview]
Message-ID: <3D86BA1B.84873680@digeo.com> (raw)
In-Reply-To: 210772234.1032213704@[10.10.2.3]

"Martin J. Bligh" wrote:
> 
> >> ...
> >> MemTotal:     32107256 kB
> >> MemFree:      27564648 kB
> >
> > I'd be suspecting that your node fallback is bust.
> >
> > Suggest you add a call to show_free_areas() somewhere; consider
> > exposing the full per-zone status via /proc with a proper patch.
> 
> Won't /proc/meminfo.numa show that? Or do you mean something
> else by "full per-zone status"?

meminfo.what?   Remember when I suggested that you put
a testing mode into the numa code so that mortals could
run numa builds on non-numa boxes?


> Looks to me like it's just out of low memory:
> 
> > LowFree:          1424 kB
> 
> There is no low memory on anything but node 0 ...
> 

It was a GFP_HIGH allocation - just pagecache.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-09-17  5:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17  4:43 dbench on tmpfs OOM's William Lee Irwin III
2002-09-17  4:43 ` William Lee Irwin III
2002-09-17  4:58 ` Andrew Morton
2002-09-17  4:58   ` Andrew Morton
2002-09-17  5:01   ` Martin J. Bligh
2002-09-17  5:01     ` Martin J. Bligh
2002-09-17  5:14     ` Andrew Morton [this message]
2002-09-17  5:14       ` Andrew Morton
2002-09-17  5:18       ` Martin J. Bligh
2002-09-17  5:18         ` Martin J. Bligh
2002-09-17  5:15   ` William Lee Irwin III
2002-09-17  5:15     ` William Lee Irwin III
2002-09-17  5:31     ` Andrew Morton
2002-09-17  5:31       ` Andrew Morton
2002-09-17  6:43       ` Christoph Rohland
2002-09-17  6:43         ` Christoph Rohland
2002-09-17  7:01       ` Hugh Dickins
2002-09-17  7:01         ` Hugh Dickins
2002-09-17  7:27         ` William Lee Irwin III
2002-09-17  7:27           ` William Lee Irwin III
2002-09-17  8:02           ` Andrew Morton
2002-09-17  8:02             ` Andrew Morton
2002-09-17 11:38             ` 35-mm1 triggers watchdog Ed Tomlinson
2002-09-17 20:12               ` Andrew Morton
2002-09-17  7:57         ` dbench on tmpfs OOM's Christoph Rohland
2002-09-17  7:57           ` Christoph Rohland
2002-12-10  5:28         ` William Lee Irwin III
2002-12-10  5:28           ` 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=3D86BA1B.84873680@digeo.com \
    --to=akpm@digeo.com \
    --cc=akpm@zip.com.au \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    --cc=wli@holomorphy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.