From: Ingo Molnar <mingo@elte.hu>
To: Stefani Seibold <stefani@seibold.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Joerg Engel <joern@logfs.org>
Subject: Re: Detailed Stack Information Patch [2/3]
Date: Wed, 1 Apr 2009 21:36:39 +0200 [thread overview]
Message-ID: <20090401193639.GB12316@elte.hu> (raw)
In-Reply-To: <1238511507.364.62.camel@matrix>
* Stefani Seibold <stefani@seibold.net> wrote:
> +config PROC_STACK_MONITOR
> + default y
> + depends on PROC_STACK
> + bool "Enable /proc/stackmon detailed stack monitoring"
> + help
> + This enables detailed monitoring of process and thread stack
> + utilization via the /proc/stackmon interface.
> + Disabling these interfaces will reduce the size of the kernel by
> + approximately 2kb.
Hm, i'm not convinced about this one. Stupid question: what's wrong
with ulimit -s?
Also, if for some reason you dont want to (or cannot) enforce a
system-wide stack size ulimit, or it has some limitation that makes
it impractical for you - if we add what i suggested to the
/proc/*/maps files, your user-space watchdog daemon could scan those
periodically and report any excesses and zap the culprit ... right?
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-04-01 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 14:58 Stefani Seibold
2009-04-01 19:36 ` Ingo Molnar [this message]
2009-04-02 21:25 ` Stefani Seibold
2009-04-03 7:32 ` Mikael Pettersson
2009-04-03 8:01 ` Stefani Seibold
2009-04-03 8:54 ` Mikael Pettersson
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=20090401193639.GB12316@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stefani@seibold.net \
/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