From: Christian Borntraeger <linux-kernel@borntraeger.net>
To: linux-kernel@vger.kernel.org
Cc: nathans@sgi.com, owner-xfs@oss.sgi.com,
"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: [STACK] >3k call path in xfs
Date: Wed, 9 Jun 2004 14:54:17 +0200 [thread overview]
Message-ID: <200406091454.21182.linux-kernel@borntraeger.net> (raw)
In-Reply-To: <20040609122647.GF21168@wohnheim.fh-wedel.de>
Jörn Engel wrote:
> 3k is not really bad yet, I just like to keep 1k of headroom for
> surprises like an extra int foo[256] in a structure.
> stackframes for call path too long (3064):
[...]
> 12 panic
[...]
I agree thats good to reduce stack size.
On the other hand I think call traces containing panic are not a call trace
I want to see at all.
cheers
Christian
next prev parent reply other threads:[~2004-06-09 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:26 [STACK] >3k call path in xfs Jörn Engel
2004-06-09 12:54 ` Christian Borntraeger [this message]
2004-06-09 13:05 ` Jörn Engel
2004-06-09 13:10 ` Jörn Engel
2004-06-09 22:58 ` Nathan Scott
2004-06-09 15:05 ` Steve Lord
2004-06-09 16:03 ` Jörn Engel
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=200406091454.21182.linux-kernel@borntraeger.net \
--to=linux-kernel@borntraeger.net \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=owner-xfs@oss.sgi.com \
/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