From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Axel Kittenberger <Axel.Kittenberger@maxxio.com>,
linux-kernel@vger.kernel.org
Cc: riel@nl.linux.org
Subject: Re: Patch: oom_kill
Date: Tue, 4 Feb 2003 08:07:03 -0600 [thread overview]
Message-ID: <200302040807.03214.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <200302041332.05096.Axel.Kittenberger@maxxio.com>
On Tuesday 04 February 2003 06:32 am, Axel Kittenberger wrote:
> A small patch to discuss, it's about killing an process in an out-of-memory
> condition. First from the code I don't see any prohibition that it kills
> init, if reaches maximum badness points, don't think thats something
> anybody anytime wants. Sure for desktop systems this very unlikely to ever
> occur, but for small embedded systems that could happen.
ok.
> Second proposal is to give processes that are direct childs from init a
> special bonus, normally that are those we don't want to get killed. They
> are either important or get respawned eitherway creating an endless oom
> condition loop when killing them.
And what about processes that get reparented to init? These could be causing
the OOM. I didn't think that the p_ptr was null when reparenting happens.
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next prev parent reply other threads:[~2003-02-04 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 12:32 Patch: oom_kill Axel Kittenberger
2003-02-04 14:07 ` Jesse Pollard [this message]
2003-02-04 14:13 ` Axel Kittenberger
2003-02-04 14:55 ` Jesse Pollard
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=200302040807.03214.pollard@admin.navo.hpc.mil \
--to=pollard@admin.navo.hpc.mil \
--cc=Axel.Kittenberger@maxxio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@nl.linux.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.