public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Yum Rayan" <yum.rayan@gmail.com>,
	linux-kernel@vger.kernel.org, mvw@planets.elm.net
Subject: Re: [PATCH] Reduce stack usage in acct.c
Date: Thu, 31 Mar 2005 22:40:39 +0200	[thread overview]
Message-ID: <20050331204039.GG3185@stusta.de> (raw)
In-Reply-To: <424C5912.90607@osdl.org>

On Thu, Mar 31, 2005 at 12:09:54PM -0800, Randy.Dunlap wrote:
> Jörn Engel wrote:
>...
> >In principle, all recursive paths should consume as little stack as
> >possible.  Or the recursion itself could be avoided, even better.  And
> >some of the call chains with ~3k of stack consumption may be
> >problematic on other platforms, like the x86-64.  Taking care of those
> >could result in smaller stacks for the respective platform.
> 
> Here is 2.6.12-rc1-bk3 raw checkstack output on x86-64:
> http://developer.osdl.org/~rddunlap/doc/checkstack1.out

Looking at the stack usage numbers, this was with a gcc that supports
unit-at-a-time.

If you use gcc 3.4 and enable unit-at-a-time (see my other email) the 
i386 numbers look quite similar.

I doubt there are many architecture or 64 bit [1] specific stack usage 
problems, so working on i386 might be enough.

> ~Randy

cu
Adrian

[1] theoretically a factor of two was possible due to the different
    pointer sizes - but I have yet to see any example where this
    really matters

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-03-31 20:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-31  7:39 [PATCH] Reduce stack usage in acct.c Yum Rayan
2005-03-31 15:05 ` Jörn Engel
2005-03-31 20:09   ` Randy.Dunlap
2005-03-31 20:40     ` Adrian Bunk [this message]
2005-03-31 20:30   ` Stack usage tasks Adrian Bunk
2005-03-31 20:43     ` Roland Dreier
2005-03-31 21:19       ` Adrian Bunk
2005-04-01 10:17         ` Jörn Engel
2005-04-01 11:16           ` Jörn Engel
2005-04-03 11:35 ` [PATCH] Reduce stack usage in acct.c Olaf Dietsche

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=20050331204039.GG3185@stusta.de \
    --to=bunk@stusta.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvw@planets.elm.net \
    --cc=rddunlap@osdl.org \
    --cc=yum.rayan@gmail.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