From: Ken Moffat <ken@kenmoffat.uklinux.net>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
riel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-pre VM regression?
Date: Mon, 20 Oct 2003 00:21:55 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.58.0310200014330.17168@ppg_penguin> (raw)
In-Reply-To: <20031016133552.GD1348@velociraptor.random>
On Thu, 16 Oct 2003, Andrea Arcangeli wrote:
>
> sure. I think I already explained there are downsides in disabling the
> oom killer for desktops where the offender task is normally the biggest
> one too, but those downsides aren't something I care about given the
> cases it gets right w/o it (i.e. huge-shm-SGA/mlock/oomdeadlocks). the
> oom killer can do the wrong decision too sometime, and more
> systematically as well.
>
Any chance of getting the oom killer back as an option ? On
2.4.23-pre7 I made the mistake of trying to print a high-resolution
photo (300ppi, A4 size) using ghostscript while I was in X. I've only
got 128MB memory and about 256MB swap on that box, which obviously
wasn't enough (gs typically uses up to 300MB for a 200ppi A4 picture).
Only problem was that X got killed instead of gs, which left the box
unuseable. Last time I saw the oom killer in action it actually saved
me from having to reboot.
Ken
--
Will code payroll for food.
next prev parent reply other threads:[~2003-10-19 23:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 11:52 Marcelo Tosatti
2003-10-16 13:15 ` Tvrtko A. Uršulin
2003-10-16 13:24 ` Andrea Arcangeli
2003-10-16 12:29 ` Marcelo Tosatti
2003-10-16 13:35 ` Andrea Arcangeli
2003-10-19 23:21 ` Ken Moffat [this message]
2003-10-21 9:25 ` Stephan von Krawczynski
2003-10-27 21:11 ` Mike Fedyk
[not found] <fa.jkt135h.1l0s0t@ifi.uio.no>
[not found] ` <fa.j3l9liv.1djudhj@ifi.uio.no>
2003-10-16 23:37 ` Andreas Hartmann
2003-10-18 22:09 A.D.F.
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=Pine.LNX.4.58.0310200014330.17168@ppg_penguin \
--to=ken@kenmoffat.uklinux.net \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.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 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®