All of lore.kernel.org
 help / color / mirror / Atom feed
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: [uml-devel] [PATCH 2/2] UML - Add stack usage monitoring
Date: Tue, 19 Jun 2007 13:14:41 -0700	[thread overview]
Message-ID: <20070619131441.01b5ae4b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070619195003.GA11718@c2.user-mode-linux.org>

On Tue, 19 Jun 2007 15:50:03 -0400
Jeff Dike <jdike@addtoit.com> wrote:

> On Tue, Jun 19, 2007 at 11:54:22AM -0700, Andrew Morton wrote:
> > On Tue, 19 Jun 2007 14:42:45 -0400
> > Jeff Dike <jdike@addtoit.com> wrote:
> > 
> > > Add a machanism to see how much of a kernel stack is used.  This
> > > allocates zeroed stacks and sees where the lowest non-zero byte is on
> > > process exit.  It keeps track of the lowest value and logs values as
> > > they get lower.
> > > 
> > 
> > remind us again why the generic code is unsuitable?
> 
> It does something different - it will tell you the greatest stack
> usage of any currently running process.  What I want to be able to do
> is run a workload and come back a few days later and see how close
> anything came to running out of stack.

<looks>

wth?  I'm _sure_ we used to have code in there which would, within
do_exit(), work out the maximum amount of kernel stack which a task had
used and if that was max-since-boot, drop a printk.

Maybe I dreamed it, but I don't think so.

I wonder where it went?

Oh well.  Your new code should really be generic, utilising the
stack-page-zeroing which CONFIG_DEBUG_STACK_USAGE enables.  There's nothing
UML-specific about it.

low_water_lock and lowest_to_date should be static to check_stack_usage(),
btw..


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

WARNING: multiple messages have this Message-ID (diff)
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 2/2] UML - Add stack usage monitoring
Date: Tue, 19 Jun 2007 13:14:41 -0700	[thread overview]
Message-ID: <20070619131441.01b5ae4b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070619195003.GA11718@c2.user-mode-linux.org>

On Tue, 19 Jun 2007 15:50:03 -0400
Jeff Dike <jdike@addtoit.com> wrote:

> On Tue, Jun 19, 2007 at 11:54:22AM -0700, Andrew Morton wrote:
> > On Tue, 19 Jun 2007 14:42:45 -0400
> > Jeff Dike <jdike@addtoit.com> wrote:
> > 
> > > Add a machanism to see how much of a kernel stack is used.  This
> > > allocates zeroed stacks and sees where the lowest non-zero byte is on
> > > process exit.  It keeps track of the lowest value and logs values as
> > > they get lower.
> > > 
> > 
> > remind us again why the generic code is unsuitable?
> 
> It does something different - it will tell you the greatest stack
> usage of any currently running process.  What I want to be able to do
> is run a workload and come back a few days later and see how close
> anything came to running out of stack.

<looks>

wth?  I'm _sure_ we used to have code in there which would, within
do_exit(), work out the maximum amount of kernel stack which a task had
used and if that was max-since-boot, drop a printk.

Maybe I dreamed it, but I don't think so.

I wonder where it went?

Oh well.  Your new code should really be generic, utilising the
stack-page-zeroing which CONFIG_DEBUG_STACK_USAGE enables.  There's nothing
UML-specific about it.

low_water_lock and lowest_to_date should be static to check_stack_usage(),
btw..


  parent reply	other threads:[~2007-06-19 20:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 18:42 [uml-devel] [PATCH 2/2] UML - Add stack usage monitoring Jeff Dike
2007-06-19 18:42 ` Jeff Dike
2007-06-19 18:54 ` [uml-devel] " Andrew Morton
2007-06-19 18:54   ` Andrew Morton
2007-06-19 19:50   ` [uml-devel] " Jeff Dike
2007-06-19 19:50     ` Jeff Dike
2007-06-19 19:57     ` [uml-devel] " Randy Dunlap
2007-06-19 19:57       ` Randy Dunlap
2007-06-20 15:37       ` [uml-devel] " Jeff Dike
2007-06-20 15:37         ` Jeff Dike
2007-06-19 20:14     ` Andrew Morton [this message]
2007-06-19 20:14       ` Andrew Morton
2007-06-20 14:06       ` [uml-devel] " Blaisorblade
2007-06-20 14:06         ` Blaisorblade
2007-06-20 15:17         ` Jeff Dike
2007-06-20 15:17           ` Jeff Dike
2007-06-20 20:20           ` Blaisorblade
2007-06-20 20:20             ` Blaisorblade
2007-06-20 18:23       ` Jeff Dike
2007-06-20 18:23         ` Jeff Dike
2007-06-20 14:18   ` [uml-devel] " Blaisorblade
2007-06-20 14:18     ` Blaisorblade
2007-06-20 15:20     ` Jeff Dike
2007-06-20 15:20       ` 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=20070619131441.01b5ae4b.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 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.