From: Thomas Gleixner <tglx@linutronix.de>
To: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Chris Ross <chris@tebibyte.org>, Andrew Morton <akpm@osdl.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Rik van Riel <riel@redhat.com>,
LKML <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, 30 Oct 2004 12:42:46 +0200 [thread overview]
Message-ID: <1099132966.22115.89.camel@thomas> (raw)
In-Reply-To: <4183649C.7070601@jp.fujitsu.com>
On Sat, 2004-10-30 at 18:53 +0900, Hiroyuki KAMEZAWA wrote:
> > Should I move your fix into the loop or move the declaration of area to
> > function scope?
> >
> Oh, Okay, my patch was wrong ;(.
> Very sorry for wrong hack.
> This one will be Okay.
It fixes at least the corrupted output of show_free_areas().
DMA: 4294966389*4kB 4294966983*8kB 4294967156*16kB .....
Normal: 4294954991*4kB 4294962949*8kB 4294965607*16kB ....
now it's
DMA: 248*4kB 63*8kB 7*16kB 1*32kB 0*64kB 0*128kB ...
Normal: 204*4kB 416*8kB 157*16kB 20*32kB 3*64kB ...
Good catch.
But it still does not fix the random madness of oom-killer. Once it is
triggered it keeps going even if there is 50MB free memory available.
tglx
next prev parent reply other threads:[~2004-10-30 10:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0410251823230.21539-100000@chimarrao.boston.redhat.com>
2004-10-25 22:33 ` Mem issues in 2.6.9 (ever since 2.6.9-rc3) and possible cause 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 [this message]
2004-10-31 12:33 ` Thomas Gleixner
2004-10-30 15:38 ` Chris Ross
2004-10-29 15:09 ` Thomas Gleixner
2004-10-23 12:59 Javier Marcet
2004-10-23 19:33 ` Andrew Morton
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
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=1099132966.22115.89.camel@thomas \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=chris@tebibyte.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kernel@kolivas.org \
--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