mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com, davidm@napali.hpl.hp.com
Cc: torvalds@transmeta.com, aebr@win.tue.nl, phillips@bonn-fries.net,
	Andries.Brouwer@cwi.nl, viro@math.psu.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH+discussion] symlink recursion
Date: Wed, 19 Jun 2002 15:06:06 -0700 (PDT)	[thread overview]
Message-ID: <20020619.150606.127425775.davem@redhat.com> (raw)
In-Reply-To: <15632.55289.204683.26908@napali.hpl.hp.com>

   From: David Mosberger <davidm@napali.hpl.hp.com>
   Date: Wed, 19 Jun 2002 12:14:01 -0700
   
   on ia-64, I see the following (2.4.18, with gcc3.1):
   
   	- ext2_follow_link():	 16 bytes/frame
   	- vfs_follow_link():	 56 bytes/frame
   	- link_path_walk():	128 bytes/frame
   	---------------------	---------------
   	total:			200 bytes/frame
   
   Just about in line with what you'd expect given that registers are
   64 bits.

On sparc64 the situation is much worse (due to register windows)
which means any non-leaf function (function which invokes no nother
functions) equals 192 bytes of stack space per frame minimum.


  reply	other threads:[~2002-06-19 22:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 22:19 Andries.Brouwer
2002-06-18 23:57 ` Linus Torvalds
2002-06-19  7:12   ` William Lee Irwin III
2002-06-19 11:48   ` Rogier Wolff
2002-06-19 14:44   ` Daniel Phillips
2002-06-19 16:05     ` Linus Torvalds
2002-06-19 18:18       ` Andries Brouwer
2002-06-19 18:55         ` Linus Torvalds
2002-06-19 19:14           ` David Mosberger
2002-06-19 22:06             ` David S. Miller [this message]
2002-06-19  7:02 Andries.Brouwer
2002-06-19 20:01 Andries.Brouwer

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=20020619.150606.127425775.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=aebr@win.tue.nl \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --cc=torvalds@transmeta.com \
    --cc=viro@math.psu.edu \
    /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®