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 17:28:29 +0200 [thread overview]
Message-ID: <20011006172829.F724@athlon.random> (raw)
In-Reply-To: <E15plMj-0002eK-00@mrvdom01.schlund.de> <20011006162617.A724@athlon.random> <E15pt4D-0002N4-00@mrvdom02.schlund.de>
In-Reply-To: <E15pt4D-0002N4-00@mrvdom02.schlund.de>; from linux-kernel@borntraeger.net on Sat, Oct 06, 2001 at 05:06:53PM +0200
On Sat, Oct 06, 2001 at 05:06:53PM +0200, Christian Bornträger wrote:
> > to test the oom killer you should try to run out of memory sometime.
>
> I used a test program with an endless dummy=new char[1024] loop.
This loop doesn't generate any page fault, it just allocates virtual
space.
> Bytheway,I had this problem without highmem - only 512 MB, and my problem is
I cannot reproduce anything like that here with 512M on 2.4.11pre3aa1.
the reports I had where all with 4G of ram, in particular with the 3.5G
of virtual memory per-process on x86 which increases the pressure on the
normal zone that in turn showed me the problem.
Anyways now that I think to have seen the issues with normal zone
faliures I will try to address them soon without having to introduce
deadlock prone code into -aa. Probably not today but I hope tomorrow or
on Monday.
Andrea
next prev parent reply other threads:[~2001-10-06 15:28 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
2001-10-06 15:06 ` Christian Bornträger
2001-10-06 15:28 ` Andrea Arcangeli [this message]
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=20011006172829.F724@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