From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Cliff White <cliffw@osdl.org>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-ac12 + kernbench == oom-killer: (OSDL)
Date: Fri, 18 Feb 2005 20:07:33 +0000 [thread overview]
Message-ID: <1108757251.17213.38.camel@localhost.localdomain> (raw)
In-Reply-To: <E1D2BPv-0006T3-Q6@es175>
On Gwe, 2005-02-18 at 16:55, Cliff White wrote:
> 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 ?
Thats showing up problems in the core code still. The OOM in this case
is because the kernel is deciding it is out of memory when it's merely
constipated with dirty pages for disk write by the look of it.
Alan
next prev parent reply other threads:[~2005-02-18 20:13 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
2005-02-18 20:07 ` Alan Cox [this message]
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=1108757251.17213.38.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aebr@win.tue.nl \
--cc=cliffw@osdl.org \
--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