public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Chris Ross <chris@tebibyte.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: slow OOM killing with 2.6.9?
Date: Thu, 16 Dec 2004 11:10:31 -0600	[thread overview]
Message-ID: <41C1C187.2040202@nortelnetworks.com> (raw)
In-Reply-To: <41C1777A.3080105@tebibyte.org>

Chris Ross wrote:

> The OOM Killer is working properly again in 2.6.10-rc2-mm4. Could you 
> try that kernel and report whether it fixed your problems too?

I had to turn off HIGHMEM support (see other response) but I mangaged to 
reproduce it.

My testcase forks a single child, then both parent and child proceed to allocate 
and write to 3/5 of total system memory.  Swap is disabled.  There is barely 
anything else running, so only one hog should have to be killed.

With 2.6.10-rc2-mm4, I got the following results:


running as root:
trial 1:
both memory hogs as well as the xterm in which they were started were killed. 
In the process, the system was frozen for 14 seconds.

trial 2: both memory hogs killed, system frozen for 9 seconds

trial 3: both memory hogs as well as the xterm in which they were started were 
killed., system was frozen for 15 seconds.

running as regular user:
trial 1:
one hog killed, system hung for 8 seconds

trial 2:
both hogs killed, timing window killed, system hung for at least 15 seconds


Doesn't look like the oom killer is entirely fixed.

Chris

      parent reply	other threads:[~2004-12-16 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 16:26 slow OOM killing with 2.6.9? Chris Friesen
2004-12-16 11:54 ` Chris Ross
2004-12-16 16:36   ` Chris Friesen
2004-12-16 17:10   ` Chris Friesen [this message]

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=41C1C187.2040202@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=chris@tebibyte.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox