All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Peter Zaitsev <peter@mysql.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VM Problems in 2.6.7 (Too active OOM Killer)
Date: Wed, 14 Jul 2004 06:10:26 +0200	[thread overview]
Message-ID: <20040714041026.GX974@dualathlon.random> (raw)
In-Reply-To: <1089776640.15336.2557.camel@abyss.home>

On Tue, Jul 13, 2004 at 08:44:02PM -0700, Peter Zaitsev wrote:
> The reason for me to disable swap both in 2.4 and 2.6 is - it really
> hurts performance. In some cases performance can be 2-3 times slower
> with swap file enabled.   Using O_DIRECT and mlock() for buffers helps 
> but not completely.

in 2.4 you can disable swap just fine (with oom killer disabled). until
I/somebody fix 2.6 you can workaround this problem while still avoiding
to swap much by setting /proc/sys/vm/swappiness to 0 or similar to tell
the VM "please don't swap" even if swap is enabled ;). That will still
prevent the oom killer to kick in. The oom killer is forbidden to run
as long as `free` tells you that >= 4k of swap are still available to the
OS. There are no other fundamental vm problems left I'm aware of in
latest 2.6 besides these no-swap and oom issues.

  reply	other threads:[~2004-07-14  4:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14  2:23 VM Problems in 2.6.7 (Too active OOM Killer) Peter Zaitsev
2004-07-14  2:40 ` William Lee Irwin III
2004-07-14  3:20   ` Peter Zaitsev
2004-07-14  3:17 ` Andrea Arcangeli
2004-07-14  3:44   ` Peter Zaitsev
2004-07-14  4:10     ` Andrea Arcangeli [this message]
2004-07-14  4:22       ` Andrew Morton
2004-07-14  4:47         ` Andrea Arcangeli
2004-07-14  4:17     ` Andrew Morton
2004-07-14 23:47       ` Peter Zaitsev
2004-07-14 22:44         ` Andrew Morton
2004-07-15  0:06           ` Andrea Arcangeli
2004-07-15  0:30           ` Peter Zaitsev
2004-07-15  0:46             ` Andrea Arcangeli
2004-07-15  1:54             ` William Lee Irwin III
2004-07-15  2:13               ` Peter Zaitsev
2004-07-15  2:33                 ` William Lee Irwin III
2004-07-15  2:39                   ` William Lee Irwin III
2004-07-15  2:44                     ` William Lee Irwin III
2004-08-13 22:23                       ` William Lee Irwin III
2004-07-19 20:27                   ` Bill Davidsen
2004-07-18 16:13               ` Kurt Garloff
2004-07-20  9:14                 ` R. J. Wysocki
2004-07-20 13:29                 ` Andrea Arcangeli
2004-07-20 13:53                   ` William Lee Irwin III
2004-07-20 13:29                 ` William Lee Irwin III
2004-07-19 20:21               ` Bill Davidsen
2004-07-15  0:04         ` Andrea Arcangeli
2004-07-15  0:43           ` Peter Zaitsev
2004-07-15  0:43           ` William Lee Irwin III
2004-07-15  1:04             ` Peter Zaitsev
2004-07-15  1:29               ` William Lee Irwin III
2004-07-14  3:50   ` William Lee Irwin III

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=20040714041026.GX974@dualathlon.random \
    --to=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@mysql.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.