From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.42-mm2
Date: Sun, 27 Oct 2002 00:32:41 -0700 [thread overview]
Message-ID: <3DBB9699.4F07BA71@digeo.com> (raw)
In-Reply-To: <20021013101949.GB2032@holomorphy.com>
William Lee Irwin III wrote:
>
> This patch does 5 things:
>
> (1) when the OOM killer fails and the system panics, calls
> show_free_areas()
> (2) reorganizes show_free_areas() to use for_each_zone()
> (3) adds per-cpu stats to show_free_areas()
> (4) tags output from show_free_areas() with node and zone information
> (5) initializes zone->per_cpu_pageset[cpu].pcp[temperature].reserved
> in free_area_init_core()
hm. I just ran out of swap and got oom-killed.
Would it make sense to call show_free_areas() for _all_ oom-killings?
I think so. At least during the development cycle.
--
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-10-27 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 6:39 2.5.42-mm2 Andrew Morton
2002-10-12 13:19 ` 2.5.42-mm2 Ed Tomlinson
2002-10-12 16:22 ` 2.5.42-mm2 Ingo Oeser
2002-10-12 17:26 ` 2.5.42-mm2 Andrew Morton
2002-10-13 10:56 ` 2.5.42-mm2 Ingo Oeser
2002-10-13 16:43 ` 2.5.42-mm2 Kai Makisara
2002-10-13 10:19 ` 2.5.42-mm2 William Lee Irwin III
2002-10-13 17:47 ` 2.5.42-mm2 Andrew Morton
2002-10-13 19:52 ` 2.5.42-mm2 William Lee Irwin III
2002-10-13 20:04 ` 2.5.42-mm2 Rik van Riel
2002-10-13 20:42 ` 2.5.42-mm2 William Lee Irwin III
2002-10-27 7:32 ` Andrew Morton [this message]
2002-10-13 21:22 ` 2.5.42-mm2 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=3DBB9699.4F07BA71@digeo.com \
--to=akpm@digeo.com \
--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