From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [PATCH 5/6] UML - Monitor stack usage
Date: Wed, 9 May 2007 21:07:38 -0700 [thread overview]
Message-ID: <20070509210738.a06b005a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070509202722.GA22464@c2.user-mode-linux.org>
On Wed, 9 May 2007 16:27:22 -0400 Jeff Dike <jdike@addtoit.com> wrote:
> In preparation for reducing stack size, add a machanism to see how
> much of a kernel stack is used. This fills a new stack with 0x6b on
> allocation and sees where the lowest non-0x6b byte is on process
> exit. It keeps track of the lowest value and logs values as they get
> lower.
but, but. We already have CONFIG_DEBUG_STACK_USAGE?
next prev parent reply other threads:[~2007-05-10 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 20:27 [PATCH 5/6] UML - Monitor stack usage Jeff Dike
2007-05-10 4:07 ` Andrew Morton [this message]
2007-05-10 11:55 ` Jeff Dike
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=20070509210738.a06b005a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.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