archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <>
Subject: Kernel call chain search tool?
Date: Tue, 24 Sep 2002 21:36:40 -0700	[thread overview]
Message-ID: <> (raw)

I have a large multithreaded program that has a habit of using too
much memory, and as a safeguard, I want to kill it before it makes
the system unstable.  The OOM killer often guesses wrong, and RLIMIT_AS
kills too soon because of the address space used up by the many thread
So I'd like an RLIMIT_RSS that just kills the fat process.

There have been a couple patches to implement RLIMIT_RSS, e.g.
Peter Chubb's
and the two from Rik, all of which are too complex for my needs
(and which only swap out instead of kill), so I guess I have to roll my

Rik's patch checks rss in handle_mm_fault(); Peter's
checked it in do_swap_page() and do_anonymous_page().
As a kernel newbie, I don't have a feel for how
those calls relate to each other.  Is there a tool 
somewhere that will take a set of function names and 
list all the kernel call chains that start in one of
the functions and end in another?

- Dan

             reply	other threads:[~2002-09-25  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25  4:36 Dan Kegel [this message]
2002-09-26 15:15 ` Alan Cox
2002-09-26 16:17   ` Dan Kegel
2002-09-26 19:07     ` Rob Landley
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: Kernel call chain search tool?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).