From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ed Sweetman <safemode@comcast.net>
Cc: Jan-Frode Myklebust <janfrode@parallab.uib.no>,
linux-kernel@vger.kernel.org
Subject: Re: OOM-killer going crazy.
Date: Tue, 27 Jul 2004 14:19:57 +1000 [thread overview]
Message-ID: <4105D7ED.5040206@yahoo.com.au> (raw)
In-Reply-To: <410500FD.8070206@comcast.net>
Ed Sweetman wrote:
> This is not the same problem as I and other are describing. There is
> no free memory when the OOM killer activates in our situation. The
> kernel has allocated all available ram and as such, the OOM killer
> can't kill the memory hog because it's the kernel, itself. So the OOM
> killer kills all the big apps running ...but it's to no use because
> the kernel just keeps trying to use more until the cd is completed.
> After which the memory is still never released.
> Your thread has nothing to do with mine.
>
I believe it could be the same problem. Jan-Frode's system has all
ZONE_NORMAL
memory used up. The free memory would be highmem which would be unsuable for
those allocations that are causing OOM.
The vfs_cache_pressure change could possibly be responsible for the
problem...
I don't have the code in front of me, but I think it divides by 100
first, then
multiplies by vfs_cache_pressure. I wouldn't have thought this would
have such
a large impact though.
next prev parent reply other threads:[~2004-07-27 4:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-25 9:46 memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) Eduard Bloch
2004-07-26 1:30 ` Ed Sweetman
2004-07-26 9:10 ` OOM-killer going crazy. (was: Re: memory not released after using cdrecord/cdrdao) Jan-Frode Myklebust
2004-07-26 10:55 ` Nick Piggin
2004-07-26 11:10 ` Jan-Frode Myklebust
2004-07-26 11:43 ` OOM-killer going crazy Nick Piggin
2004-07-26 12:46 ` Jan-Frode Myklebust
2004-07-27 1:00 ` Nick Piggin
2004-07-26 13:02 ` Ed Sweetman
2004-07-27 4:19 ` Nick Piggin [this message]
2004-07-27 10:07 ` Jens Axboe
2004-07-27 13:23 ` Ed Sweetman
2004-07-27 13:30 ` Nick Piggin
2004-07-27 22:38 ` Ed Sweetman
2004-07-28 1:00 ` Nick Piggin
2004-07-28 6:30 ` Ed Sweetman
2004-07-28 6:45 ` Jens Axboe
2004-07-28 12:58 ` Ed Sweetman
2004-07-28 13:31 ` Jens Axboe
2004-07-29 0:08 ` memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) 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=4105D7ED.5040206@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=janfrode@parallab.uib.no \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@comcast.net \
/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.