linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-mm@kvack.org
Subject: Re: [1/13] add __GFP_NOKILL
Date: Wed, 25 Sep 2002 23:26:05 -0700	[thread overview]
Message-ID: <3D92A87D.3BB631B9@digeo.com> (raw)
In-Reply-To: <20020926054220.GH22942@holomorphy.com>

Andrea just disabled out_of_memory().

We need to find out why these oom-killings are happening
in the first place.  They probably all have a common cause.

Please arrange to dump the state of all zones and page_states[]
when it happens.

Adding:

static struct page_state wli_state;

get_page_state(struct page_state *ps)
{
	...
	*wli = *ps;
	return;
}

in page_alloc.c makes the latter easier.

As we discussed, be suspicious of your fallback lists.  Otherwise
it _might_ be the zone-unaware throttling.  I want to know, please,
before I go and add lots of sleep/wakeup gunk to try_to_free_pages()
and end_page_writeback().

Critical question: how much dirty memory is in the normal
zone?  To determine this, look at the last three functions
in mm/page_writeback.c.  Make them do

	atomic_inc/dec(&page_zone(page)->nr-dirty);

thanks.

Also it is important to know the size of the active/inactive
lists in those zones.
--
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/

      parent reply	other threads:[~2002-09-26  6:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26  5:42 William Lee Irwin III
2002-09-26  5:51 ` William Lee Irwin III
2002-09-26  6:26 ` Andrew Morton [this message]

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=3D92A87D.3BB631B9@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