From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Byron Stanoszek <gandalf@winds.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [STACK] >3k call path in ncpfs
Date: Wed, 9 Jun 2004 20:27:06 +0200 [thread overview]
Message-ID: <20040609182706.GC2950@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.60.0406091414140.14198@winds.org>
On Wed, 9 June 2004 14:15:19 -0400, Byron Stanoszek wrote:
>
> Jörn, do you have any analysis of stack usage for x86-64 or other 64-bit
> processors? I assume they would more readily reach the 4K stack boundaries
> as all longs and pointers are 8 bytes instead of 4.
No I don't, the tool isn't even tested on anything but i386. Do any
64bit architectures use 4k stacks?
Jörn
--
If you're willing to restrict the flexibility of your approach,
you can almost always do something better.
-- John Carmack
next prev parent reply other threads:[~2004-06-09 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:20 Jörn Engel
2004-06-09 18:15 ` Byron Stanoszek
2004-06-09 18:27 ` Jörn Engel [this message]
2004-06-09 18:31 ` Byron Stanoszek
2004-06-10 0:06 ` [PATCH] Decrease stack usage in ncpfs's ioctl (was Re: [STACK] >3k call path in ncpfs) Petr Vandrovec
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=20040609182706.GC2950@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=gandalf@winds.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®