From: Sven Heinicke <sven@research.nj.nec.com>
To: linux-kernel@vger.kernel.org
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Ben Smith <ben@google.com>, Andrea Arcangeli <andrea@suse.de>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: Google's mm problem - not reproduced on 2.4.13
Date: Fri, 2 Nov 2001 12:51:09 -0500 (EST) [thread overview]
Message-ID: <15330.56589.291830.542215@abasin.nj.nec.com> (raw)
In-Reply-To: <3BE07730.60905@google.com>
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>
Ben Smith writes:
> > On October 31, 2001 09:45 pm, Andrea Arcangeli wrote:
> >
> >>On Wed, Oct 31, 2001 at 09:39:12PM +0100, Daniel Phillips wrote:
> >>
> >>>On October 31, 2001 07:06 pm, Daniel Phillips wrote:
> >>>
> >>>>I just tried your test program with 2.4.13, 2 Gig, and it ran
> >>>>without problems. Could you try that over there and see if you
> >>>>get the same result? If it does run, the next move would be to
> >>>>check with 3.5 Gig.
> >>>>
> >>>Ben reports that his test with 2 Gig memory runs fine, as it does
> >>>for me, but that it locks up tight with 3.5 Gig, requiring power
> >>>cycle. Since I only have 2 Gig here I can't reproduce that (yet).
> >>>
> >>are you sure it isn't an oom condition. can you reproduce on
> >>2.4.14pre5aa1? mainline (at least before pre6) could deadlock with
> >>too much mlocked memory.
> >>
> >
> > I don't know, I can't reproduce it here, I don't have enough memory.
> > Ben?
>
> 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.
> - Ben
>
> Ben Smith
> Google, Inc
>
This is a System with 4G of memory and regular swap. With 2 Pentium
III 1Ghz processors.
On 2.4.14-pre6aa1 it happily runs until:
munmap'ed 7317d000
Loading data at 7317d000 for slot 2
Load (/mnt/sdb/sven/chunk10) succeeded!
mlocking slot 2, 7317d000
mlocking at 7317d000 of size 1048576
Connection to hera closed by remote host.
Connection to hera closed.
Where is kills my ssh and other programs. fills my /var/log/messages
with:
Nov 2 11:29:07 ps2 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Nov 2 11:29:07 ps2 syslogd: select: Cannot allocate memory
Nov 2 11:29:07 ps2 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Nov 2 11:29:07 ps2 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Nov 2 11:29:07 ps2 last message repeated 2 times
a bunch of times. Then doesn't free the mmaped memory until file
system is unmounted. It never starts going into swap.
2.4.14-pre5aa1 does about the same.
Sven
next prev parent reply other threads:[~2001-11-02 17:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 18:06 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
2001-11-02 17:51 ` Sven Heinicke [this message]
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=15330.56589.291830.542215@abasin.nj.nec.com \
--to=sven@research.nj.nec.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®