public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: "Christian Bornträger" <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: OOM-Killer in 2.4.11pre4
Date: Sat, 6 Oct 2001 16:26:17 +0200	[thread overview]
Message-ID: <20011006162617.A724@athlon.random> (raw)
In-Reply-To: <E15plMj-0002eK-00@mrvdom01.schlund.de>
In-Reply-To: <E15plMj-0002eK-00@mrvdom01.schlund.de>; from linux-kernel@borntraeger.net on Sat, Oct 06, 2001 at 08:53:30AM +0200

On Sat, Oct 06, 2001 at 08:53:30AM +0200, Christian Bornträger wrote:
> I reported __alloc_pages: 0-order allocation failed errors in 2.4.10 with a 
> memory eating program. 
> 
> These errors are gone with 2.4.11pre4. The OOM-Killer works __correct__.  it 
> seems that Marcelos Patch works correct for me.

to test the oom killer you should try to run out of memory sometime.
It's not the oom killer that cured the oom faliures, it is the deadlock
prone infinite loop in the allocator that did.

Now I identified various issues that can explain the oom faliures on the
highmem boxes (I don't have any highmem box so it wasn't possible to
trigger them here, the higher memory ia32 machine that I own is my
UP desktop with 512mbyte of ram), and I will be able to verify my fixes
as soon as I can get a login on a 4/8G box. I created this project for
this purpose:

	http://www.osdlab.org/cgi-bin/eidetic.cgi?command=display&modulename=projects&on=60

After I get the login and after verifying my fixes I'll release a new
-aa that will be meant primarly to fix the allocation faliures.

Andrea

  reply	other threads:[~2001-10-06 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06  6:53 OOM-Killer in 2.4.11pre4 Christian Bornträger
2001-10-06 14:26 ` Andrea Arcangeli [this message]
2001-10-06 15:06   ` Christian Bornträger
2001-10-06 15:28     ` Andrea Arcangeli
2001-10-08 16:12   ` Marcelo Tosatti

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=20011006162617.A724@athlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@borntraeger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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