From: Rob Landley <landley@trommello.org>
To: Dan Kegel <dank@kegel.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel call chain search tool?
Date: Thu, 26 Sep 2002 15:07:38 -0400 [thread overview]
Message-ID: <20020927000451.98A9E398@merlin.webofficenow.com> (raw)
In-Reply-To: <3D93331C.86F87359@kegel.com>
On Thursday 26 September 2002 12:17 pm, Dan Kegel wrote:
> If only the darn program didn't have so many threads, RLIMIT_AS
> or the no-overcommit patch would be perfect. I unfortunately can't
> get rid of the threads, so I'm stuck trying to figure out some way
> to kill the right program when the system gets low on memory.
>
> Maybe I should look at giving the OOM killer hints?
The OOM killer should certainly know about threads and thread groups. If you
kill one thread, you generally have to kill the whole group because there's
no way of knowing if that thread was holding a futex or otherwise custodian
of critical data and thus you just threw the program into la-la land.
> - Dan
Rob
next prev parent reply other threads:[~2002-09-27 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 4:36 Kernel call chain search tool? Dan Kegel
2002-09-26 15:15 ` Alan Cox
2002-09-26 16:17 ` Dan Kegel
2002-09-26 19:07 ` Rob Landley [this message]
2002-09-27 0:39 ` OOM killer hints (was: Re: Kernel call chain search tool?) Dan Kegel
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=20020927000451.98A9E398@merlin.webofficenow.com \
--to=landley@trommello.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dank@kegel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).