mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Bless <bless@tm.uka.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Roland Bless <bless@tm.uka.de>,
	miquels@cistron.nl, linux-kernel@vger.kernel.org,
	walter@tm.uka.de, winter@tm.uka.de, doll@tm.uka.de
Subject: Re: Fix for wrong OOM killer trigger?
Date: Sat, 20 Sep 2003 13:09:28 +0200	[thread overview]
Message-ID: <20030920110928.GA24934@vorta.ipv6.tm.uka.de> (raw)
In-Reply-To: <20030919192544.GC1312@velociraptor.random>

On Fri, Sep 19, 2003 at 09:25:44PM +0200, Andrea Arcangeli wrote:
> 
> can you try with 2.4.22aa1? the oom killer there will only work on tasks
> that are allocating memory, not on idle daemons, so the probability of
> killing rsync first should be higher. stock SuSE 8.1 kernel should do
> the same too.

This will only help to avoid not shooting important daemons.
The real cause, however, seems to be that the filesystem cache
memory is not properly re-used when it should, or, that it tries to
allocate a huge amount memory. The programs themselves do not
allocate much memory! It must be the system, because I also
ran programs with memory restrictions by ulimit. The programs
are definitely not allocating the memory, and, 4GB RAM are really
enough for a simple file server like ours.

Regards,
 Roland

  parent reply	other threads:[~2003-09-20 11:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 17:16 Roland Bless
2003-09-19 17:30 ` Marc-Christian Petersen
2003-09-19 19:25 ` Andrea Arcangeli
2003-09-19 19:35   ` Russell King
2003-09-19 20:01     ` Andrea Arcangeli
2003-09-19 20:52       ` Larry McVoy
2003-09-19 21:05         ` Formal complaint , " Mr. James W. Laferriere
2003-09-20  6:36           ` David S. Miller
2003-09-20  3:31         ` Andrea Arcangeli
2003-09-20  4:30           ` Larry McVoy
2003-09-20 12:22             ` Bernd Schmidt
2003-09-20 13:52               ` Willy Tarreau
2003-09-20 13:54               ` Larry McVoy
2003-09-20 19:56                 ` Gateways (was Re: Fix for wrong OOM killer trigger?) Jamie Lokier
2003-09-20 20:14                   ` Larry McVoy
2003-09-21 11:52                     ` David S. Miller
2003-09-20 16:07               ` Fix for wrong OOM killer trigger? Valdis.Kletnieks
2003-09-20 14:23             ` Andrea Arcangeli
2003-09-20 15:13               ` Larry McVoy
2003-09-20 17:14                 ` Flames (was: Fix for wrong OOM killer trigger?) Stephen Satchell
2003-09-20 17:46                   ` Alan Cox
2003-09-21 10:40                 ` Fix for wrong OOM killer trigger? Eric W. Biederman
2003-09-21 14:22                   ` Andrea Arcangeli
2003-09-21 14:52                     ` Larry McVoy
2003-09-21 15:53                       ` Andrea Arcangeli
2003-09-23 12:46                     ` Bas Mevissen
2003-09-20 11:09   ` Roland Bless [this message]
2003-09-20 14:34     ` Andrea Arcangeli
2003-09-22 10:11       ` Roland Bless
2003-09-22 13:02         ` Andrea Arcangeli

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=20030920110928.GA24934@vorta.ipv6.tm.uka.de \
    --to=bless@tm.uka.de \
    --cc=andrea@suse.de \
    --cc=doll@tm.uka.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    --cc=walter@tm.uka.de \
    --cc=winter@tm.uka.de \
    /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®