From: Andrea Arcangeli <andrea@suse.de>
To: Ben Smith <ben@google.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
linux-kernel@vger.kernel.org,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: Google's mm problem - not reproduced on 2.4.13
Date: Thu, 1 Nov 2001 01:34:37 +0100 [thread overview]
Message-ID: <20011101013437.L1291@athlon.random> (raw)
In-Reply-To: <E15yzlQ-00021P-00@starship.berlin> <E15z28m-0000vb-00@starship.berlin> <20011031214540.D1291@athlon.random> <E15z2WJ-0000wc-00@starship.berlin> <3BE07730.60905@google.com>
In-Reply-To: <3BE07730.60905@google.com>; from ben@google.com on Wed, Oct 31, 2001 at 02:12:00PM -0800
On Wed, Oct 31, 2001 at 02:12:00PM -0800, Ben Smith wrote:
> My test application gets killed (I believe by the oom handler). dmesg
> complains about a lot of 0-order allocation failures. For this test,
> I'm running with 2.4.14pre5aa1, 3.5gb of RAM, 2 PIII 1Ghz.
Interesting, now we need to find out if the problem is the allocator in
2.4.14pre5aa1 that fails too early by mistake, or if this is a true oom
condition. I tend to think it's a true oom condition since mainline
deadlocked under the same workload where -aa correctly killed the task.
Can you provide also a 'vmstat 1' trace of the last 20/30 seconds before
the task gets killed?
A true oom condition could be caused by a memleak in mlock or something
like that (or of course it could be a bug in the userspace testcase, but
I checked the testcase a few weeks ago and I didn't found anything wrong
in it).
Andrea
next prev parent reply other threads:[~2001-11-01 0:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 18:06 Google's mm problem - not reproduced on 2.4.13 Daniel Phillips
2001-10-31 20:39 ` Daniel Phillips
2001-10-31 20:45 ` Andrea Arcangeli
2001-10-31 21:03 ` Daniel Phillips
2001-10-31 21:53 ` Andreas Dilger
2001-11-01 4:52 ` Daniel Phillips
2001-11-01 16:56 ` undefined reference in 2.2.19 build with Reiserfs (was: Google's mm problem - not reproduced on 2.4.13) Sven Heinicke
2001-11-01 22:39 ` Keith Owens
2001-10-31 22:12 ` Google's mm problem - not reproduced on 2.4.13 Ben Smith
2001-11-01 0:34 ` Andrea Arcangeli [this message]
2001-11-02 17:51 ` Sven Heinicke
2001-11-02 18:00 ` Andrea Arcangeli
2001-11-02 18:19 ` Daniel Phillips
2001-11-02 20:27 ` Linus Torvalds
2001-11-02 21:08 ` Ben Smith
2001-11-02 21:20 ` Linus Torvalds
2001-11-02 22:42 ` Ben Smith
2001-11-02 23:15 ` Daniel Phillips
2001-11-03 22:53 ` Adaptec vs Symbios performance Stephan von Krawczynski
2001-11-03 23:01 ` arjan
2001-11-02 21:12 ` Google's mm problem - not reproduced on 2.4.13 Rik van Riel
[not found] ` <200111022027.fA2KRwe20006@penguin.transmeta.com>
2001-11-02 20:58 ` Daniel Phillips
2001-11-02 18:11 ` Daniel Phillips
2001-11-02 18:48 ` Sven Heinicke
2001-11-02 18:57 ` Daniel Phillips
2001-11-01 0:19 ` Daniel Phillips
2001-11-01 0:29 ` Andrea Arcangeli
2001-11-01 1:17 ` Ben Smith
2001-11-01 1:41 ` Rik van Riel
2001-11-01 1:55 ` Ben Smith
2001-11-01 2:06 ` Andrea Arcangeli
2001-10-31 20:48 ` Rik van Riel
2001-10-31 21:04 ` Daniel Phillips
2001-10-31 21:08 ` Rik van Riel
[not found] <Pine.LNX.4.33.0111021250560.20078-100000@penguin.transmeta.com>
2001-11-02 21:13 ` Linus Torvalds
2001-11-02 21:27 ` Stephan von Krawczynski
2001-11-03 0:16 ` Linus Torvalds
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=20011101013437.L1291@athlon.random \
--to=andrea@suse.de \
--cc=ben@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.