All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Kevin Shanahan <kmshanah@ucwb.org.au>, linux-kernel@vger.kernel.org
Subject: Re: OOM (HighMem) on linux 2.6.24.2
Date: Tue, 01 Apr 2008 06:57:27 +0200	[thread overview]
Message-ID: <1207025847.8514.675.camel@twins> (raw)
In-Reply-To: <200804010431.11271.vda.linux@googlemail.com>

On Tue, 2008-04-01 at 04:31 +0200, Denys Vlasenko wrote:
> On Thursday 20 March 2008 11:04, Kevin Shanahan wrote:
> > Feb 28 06:32:20 hermes kernel: 5313 pages slab
> > Feb 28 06:32:20 hermes kernel: 2632 pages pagetables
> > Feb 28 06:32:20 hermes kernel: Out of memory: kill process 24013 (apache2) score 22070 or a child
> > Feb 28 06:32:20 hermes kernel: Killed process 24013 (apache2)
> > 
> > Looks like the HighMem low watermark was hit again (though I've no idea
> > if that's actually significant).
> 
> I kno that people routinely forget to do that, but
> at least for purely paranoid reasons you are better
> to run all daemons with setrlimit'ed memory size.
> At least all daemons which you cannot reasonably
> trust to be 100% leak-free and to have bounded
> peak memory usage.

Afaik we don't actually implement RLIMIT_RSS.


  reply	other threads:[~2008-04-01  4:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  0:48 OOM (HighMem) on linux 2.6.24.2 Kevin Shanahan
2008-03-20  8:44 ` Jiri Slaby
2008-03-20  8:44   ` Jiri Slaby
2008-03-20 10:17   ` Kevin Shanahan
2008-03-20 10:17     ` Kevin Shanahan
2008-03-20  8:54 ` Peter Zijlstra
2008-03-20 10:04   ` Kevin Shanahan
2008-04-01  2:31     ` Denys Vlasenko
2008-04-01  4:57       ` Peter Zijlstra [this message]
2008-04-01  8:17         ` Denys Vlasenko
2008-04-01  8:38           ` KOSAKI Motohiro

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=1207025847.8514.675.camel@twins \
    --to=peterz@infradead.org \
    --cc=kmshanah@ucwb.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda.linux@googlemail.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 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.