Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Le Rouzic <aime.le-rouzic@bull.net>
Cc: nfs@lists.sourceforge.net, nfsv4 <nfsv4@linux-nfs.org>
Subject: Re: [NFS] "used greatest stack depth: n bytes left" messages
Date: Wed, 12 Sep 2007 15:13:44 -0400	[thread overview]
Message-ID: <20070912191344.GB13792@fieldses.org> (raw)
In-Reply-To: <46E7E170.8000903@bull.net>

On Wed, Sep 12, 2007 at 02:54:08PM +0200, Le Rouzic wrote:
>   CONFIG_DEBUG_STACK_USAGE was already set in my previous kernel configuration
>   but those messages are new  but like you wrote more for debug warning.
>   Nevertheless the question was more to know if they mean some degradation
>   happening. So far, it looks not.

Right, it doesn't necessarily mean anything, it's just telling you the
number of bytes that weren't used on the stack.  If you've got thousands
of bytes left:

> >>Sep 11 12:22:40 frec kernel: loadkeys used greatest stack depth: 4568
> >>bytes left
> >>Sep 11 12:22:40 frec kernel: rc.sysinit used greatest stack depth: 4448
> >>bytes left
> >>Sep 11 12:22:40 frec kernel: readahead used greatest stack depth: 4264
> >>bytes left
> >>Sep 11 13:38:36 frec kernel: mount.nfs4 used greatest stack depth: 4088
> >>bytes left
> >>Sep 11 17:12:08 frec kernel: mount.nfs4 used greatest stack depth: 3512
> >>bytes left

then nothing's coming anywhere near overflowing its stack, so that's
good.  (But do you know what stack size your kernel is using?  I guess
it's >4k, so probably 8k, suggesting some of these processes are using
over 4k, which seems like a lot.)

--b.

      reply	other threads:[~2007-09-12 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 11:27 "used greatest stack depth: n bytes left" messages Le Rouzic
2007-09-12 12:10 ` Kevin Coffman
2007-09-12 12:54   ` [NFS] " Le Rouzic
2007-09-12 19:13     ` J. Bruce Fields [this message]

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=20070912191344.GB13792@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aime.le-rouzic@bull.net \
    --cc=nfs@lists.sourceforge.net \
    --cc=nfsv4@linux-nfs.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