From: Le Rouzic <aime.le-rouzic@bull.net>
To: nfsv4 <nfsv4@linux-nfs.org>, nfs@lists.sourceforge.net
Subject: "used greatest stack depth: n bytes left" messages
Date: Wed, 12 Sep 2007 13:27:45 +0200 [thread overview]
Message-ID: <46E7CD31.4080306@bull.net> (raw)
Hi,
Since 2.6.23-RC5 we can get the following kind of messages in
/var/log/messages:
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
Are there only WARNINGs?
Does that mean we need to act on some kernel parameter ? Which one?
Can we conclude anything is not normal?
How nfsv4 can be impacted in its behavior?
Cheers
--
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name : Aime Le Rouzic
Mail : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail : aime.le-rouzic@bull.net
Phone : 33 (4) 76.29.75.51
Fax : 33 (4) 76.29.75.18
-----------------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-09-12 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 11:27 Le Rouzic [this message]
2007-09-12 12:10 ` "used greatest stack depth: n bytes left" messages Kevin Coffman
2007-09-12 12:54 ` [NFS] " Le Rouzic
2007-09-12 19:13 ` J. Bruce Fields
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=46E7CD31.4080306@bull.net \
--to=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