From: Cliff White <cliffw@osdl.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.6.10-ac12 + kernbench == oom-killer: (OSDL)
Date: Fri, 18 Feb 2005 08:55:47 -0800 [thread overview]
Message-ID: <E1D2BPv-0006T3-Q6@es175> (raw)
In-Reply-To: <20050209013617.GC2686@pclin040.win.tue.nl>
> On Tue, Feb 08, 2005 at 02:57:07PM -0800, cliff white wrote:
>
> > Running 2.6.10-ac10 on the STP 1-CPU machines, we don't seem to be able to
> complete
> > a kernbench run without hitting the OOM-killer. ( kernbench is multiple ker
> nel compiles,
> > of course ) Machine is 800 mhz PIII with 1GB memory. We reduce memory for s
> ome of the runs.
> >
> > Typical results:
> >
> > Out of Memory: Killed process 14970 (cc1).
> > -------------------------
> > It looks like some oom-related stuff went into -ac10, will try retest with
> > -ac9 and -ac10, see what happens. Lemme know if we can do more
>
> I am always curious to hear how things are when you set
> /proc/sys/vm/overcommit_memory to 2
> (and possibly /proc/sys/vm/overcommit_ratio to something
> appropriate).
Okay, with just vm.overcommit=2, things are still bad:
http://khack.osdl.org/stp/300854/logs/TestRunFailed.console.log.txt
Suggestion for vm.overcommit_ratio ?
Or should i repeat with later -ac ?
cliffw
-----------Some output---------------
Free pages: 8872kB (0kB HighMem)
Active:14865 inactive:4118 dirty:0 writeback:629 unstable:0 free:2218 slab:11489 mapped:32027 pagetables:13800
DMA free:1224kB min:128kB low:160kB high:192kB active:552kB inactive:196kB present:16384kB pages_scanned:401 all_unreclaimable? no
protections[]: 0 0 0
Normal free:7648kB min:1920kB low:2400kB high:2880kB active:58908kB inactive:16276kB present:245760kB pages_scanned:1395 all_unreclaimable? no
protections[]: 0 0 0
HighMem free:0kB min:128kB low:160kB high:192kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
protections[]: 0 0 0
DMA: 240*4kB 17*8kB 2*16kB 1*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 1224kB
Normal: 1348*4kB 46*8kB 54*16kB 6*32kB 1*64kB 0*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 7648kB
HighMem: empty
Swap cache: add 23226854, delete 23224756, find 324015/2933249, race 2549+2365
Out of Memory: Killed process 14667 (rpm).
oom-killer: gfp_mask=0xd2
DMA per-cpu:
cpu 0 hot: low 2, high 6, batch 1
cpu 0 cold: low 0, high 2, batch 1
Normal per-cpu:
cpu 0 hot: low 30, high 90, batch 15
cpu 0 cold: low 0, high 30, batch 15
HighMem per-cpu: empty
------------------
cliffw
>
> Andries
>
next prev parent reply other threads:[~2005-02-18 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 22:57 2.6.10-ac12 + kernbench == oom-killer: (OSDL) cliff white
2005-02-09 1:36 ` Andries Brouwer
2005-02-18 16:55 ` Cliff White [this message]
2005-02-18 20:07 ` Alan Cox
2005-02-21 17:15 ` cliff white
2005-02-09 12:12 ` Marcelo Tosatti
2005-02-17 20:49 ` cliff white
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=E1D2BPv-0006T3-Q6@es175 \
--to=cliffw@osdl.org \
--cc=aebr@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).