All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Javier Marcet <javier@marcet.info>
Cc: linux-kernel@vger.kernel.org, kernel@kolivas.org
Subject: Re: Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause
Date: Sat, 23 Oct 2004 12:33:23 -0700	[thread overview]
Message-ID: <20041023123323.04b59353.akpm@osdl.org> (raw)
In-Reply-To: <20041023125948.GC9488@marcet.info>

Javier Marcet <javier@marcet.info> wrote:
>
> I've been following quite closely the development of 2.6.9, testing
>  every -rc release and a lot of -bk's.
> 
>  Upon changing from 2.6.9-rc2 to 2.6.9-rc3 I began experiencing random
>  oom kills whenever a high memory i/o load took place.

Do you have swap online?

What sort of machine is it, and how much memory has it?

>  This happened with plenty of free memory, and with whatever values I
>  used for vm.overcommit_ratio and vm.overcommit_memory
>  Doubling the physical RAM didn't change the situation either.
> 
>  Having traced the problem to 2.6.9-rc3, I took a look at the differences
>  in memory handling between 2.6.9-rc2 and 2.6.9-rc3 and with the attached
>  patch I have no more oom kills. Not a single one.
> 
>  I'm not saying everything within the patch is needed, not even that it's
>  the right thing to change. Nonetheless, 2.6.9 vanilla was unusable,
>  while this avoids those memory leaks.

That patch only affects NUMA machines?

  reply	other threads:[~2004-10-23 19:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 12:59 Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause Javier Marcet
2004-10-23 19:33 ` Andrew Morton [this message]
2004-10-23 23:03   ` Con Kolivas
2004-10-25 21:51 ` Rik van Riel
2004-10-25 22:13   ` Andrew Morton
2004-10-26  8:01     ` Nick Piggin
2004-10-29 22:39 ` Thomas Gleixner
     [not found] <Pine.LNX.4.44.0410251823230.21539-100000@chimarrao.boston.redhat.com>
2004-10-25 22:33 ` Rik van Riel
2004-10-28 12:06   ` Marcelo Tosatti
2004-10-28 15:27     ` Chris Ross
2004-10-28 15:01       ` Marcelo Tosatti
2004-10-29 13:36     ` Chris Ross
2004-10-29 14:46       ` Chris Ross
2004-10-30  8:25       ` Hiroyuki KAMEZAWA
2004-10-30  8:45         ` Chris Ross
2004-10-30  8:58           ` Hiroyuki KAMEZAWA
2004-10-30  9:30             ` Chris Ross
2004-10-30  9:53               ` Hiroyuki KAMEZAWA
2004-10-30 10:42                 ` Thomas Gleixner
2004-10-31 12:33                   ` Thomas Gleixner
2004-10-30 15:38                 ` Chris Ross
2004-10-29 15:09     ` Thomas Gleixner

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=20041023123323.04b59353.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=javier@marcet.info \
    --cc=kernel@kolivas.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 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.