From: William Lee Irwin III <wli@holomorphy.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.74-mm3 OOM killer fubared ?
Date: Thu, 10 Jul 2003 04:27:28 -0700 [thread overview]
Message-ID: <20030710112728.GX15452@holomorphy.com> (raw)
In-Reply-To: <bejhrj$dgg$1@news.cistron.nl>
On Thu, Jul 10, 2003 at 11:14:59AM +0000, Miquel van Smoorenburg wrote:
> Enough memory free, no problems at all .. yet every few minutes
> the OOM killer kills one of my innfeed processes.
> I notice that in -mm3 this was deleted relative to -vanilla:
>
> -
> - /*
> - * Enough swap space left? Not OOM.
> - */
> - if (nr_swap_pages > 0)
> - return;
> .. is that what causes this ? In any case, that should't vene matter -
> there's plenty of memory in this box, all buffers and cached, but that
> should be easily freed ..
This means we're calling into it more often than we should be.
Basically, we hit __alloc_pages() with __GFP_WAIT set, find nothing
we're allowed to touch, dive into try_to_free_pages(), fall through
scanning there, sleep in blk_congestion_wait(), wake up again, try
to shrink_slab(), find nothing there either, repeat that 11 more times,
and then fall through to out_of_memory()... and this happens at at
least 10Hz.
since = now - lastkill;
if (since < HZ*5)
goto out_unlock;
try s/goto out_unlock/goto reset/ and let me know how it goes.
-- wli
next prev parent reply other threads:[~2003-07-10 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 11:14 2.5.74-mm3 OOM killer fubared ? Miquel van Smoorenburg
2003-07-10 11:27 ` William Lee Irwin III [this message]
2003-07-10 12:54 ` Miquel van Smoorenburg
2003-07-10 13:34 ` Richard B. Johnson
2003-07-10 13:45 ` Miquel van Smoorenburg
2003-07-10 14:32 ` Rik van Riel
2003-07-10 17:43 ` Mikulas Patocka
2003-07-10 15:56 ` William Lee Irwin III
2003-07-10 23:05 ` Miquel van Smoorenburg
2003-07-11 1:01 ` William Lee Irwin III
2003-07-10 17:38 ` Andrew Morton
2003-07-10 23:31 ` Miquel van Smoorenburg
2003-07-10 17:46 ` Mikulas Patocka
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=20030710112728.GX15452@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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.