From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Manish Neema <Manish.Neema@synopsys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: System hang problem.
Date: Wed, 04 Oct 2006 01:33:14 +0100 [thread overview]
Message-ID: <1159921995.17553.136.camel@localhost.localdomain> (raw)
In-Reply-To: <C9A861D62D068643A0F4A7B1BCB38E2C0327B5A0@US01WEMBX1.internal.synopsys.com>
Ar Maw, 2006-10-03 am 15:07 -0700, ysgrifennodd Manish Neema:
> RHEL3.0 U3 would generate an OOM kill "each and every time" it sensed
> system hang but due to other bugs, we had to move away from it. RedHat
And often when it didn't need too which for many users workloads is bad
> Changing overcommit to 2 (and ratio to any where from 1 to 99) would
> result in certain OS processes (automount daemon for e.g.) getting
> killed when all the allowed memory is committed. What is the point in
Killed and logging an OOM message ? That indicates a bug (well for ratio
<= about 50% anyway). Killed because there is no memory and a memory
allocation fails is expected.
> reserving some memory if a random root process would get killed leaving
> the system in a totally unknown state?
If you run out of memory and someone asks for more something has to
give. A properly configured system really shouldn't be running out of
memory anyway for most sane workloads.
It's like putting water in a bottle, at the point you have more water
than bottle something has to spill, if it doesn't the box hangs.
Alan
next prev parent reply other threads:[~2006-10-04 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 22:07 System hang problem Manish Neema
2006-10-03 23:35 ` Keith Mannthey
2006-10-04 0:33 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 0:07 Manish Neema
2006-10-04 0:49 ` Alan Cox
2006-10-04 3:26 ` Willy Tarreau
2006-10-04 9:53 ` Jarek Poplawski
2006-10-04 5:44 Manish Neema
2006-10-04 14:24 Al Boldi
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=1159921995.17553.136.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Manish.Neema@synopsys.com \
--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.