From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-mm@kvack.org, hugh@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: dbench on tmpfs OOM's
Date: Mon, 16 Sep 2002 22:31:59 -0700 [thread overview]
Message-ID: <3D86BE4F.75C9B6CC@digeo.com> (raw)
In-Reply-To: <20020917051501.GM3530@holomorphy.com>
William Lee Irwin III wrote:
>
> William Lee Irwin III wrote:
> >> MemTotal: 32107256 kB
> >> MemFree: 27564648 kB
>
> On Mon, Sep 16, 2002 at 09:58:43PM -0700, Andrew Morton wrote:
> > 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.
>
> I went through the nodes by hand. It's just a run of the mill
> ZONE_NORMAL OOM coming out of the GFP_USER allocation. None of
> the highmem zones were anywhere near ->pages_low.
>
erk. Why is shmem using GFP_USER?
mnm:/usr/src/25> grep page_address mm/shmem.c
mnm:/usr/src/25>
--
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/
next prev parent reply other threads:[~2002-09-17 5:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 4:43 William Lee Irwin III
2002-09-17 4:58 ` Andrew Morton
2002-09-17 5:01 ` Martin J. Bligh
2002-09-17 5:14 ` Andrew Morton
2002-09-17 5:18 ` Martin J. Bligh
2002-09-17 5:15 ` William Lee Irwin III
2002-09-17 5:31 ` Andrew Morton [this message]
2002-09-17 6:43 ` Christoph Rohland
2002-09-17 7:01 ` Hugh Dickins
2002-09-17 7:27 ` William Lee Irwin III
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-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=3D86BE4F.75C9B6CC@digeo.com \
--to=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox