Re: [2.6 patch] i386: always use 4k stacks

[Jörn Engel]

On Wed, 30 November 2005 03:31:13 -0700, Eric W. Biederman wrote:
> Kenneth Parrish <Kenneth.Parrish@xxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:
> 
> > -=> In article 16 Nov 05  14:40:16, Adrian Bunk wrote to All <=-
> >
> >  AB> If one function calls another function you have to add the stack
> >  AB> usages.
> >
> > these few may do that, i bet.
> >  0xc02bb528 huft_build:                                  1432
> >  0xc02bb954 huft_build:                                  1432
> >  0xc02bc1c4 inflate_dynamic:                             1312
> >  0xc02bc2ff inflate_dynamic:                             1312
> >  0xc02bc082 inflate_fixed:                               1168
> >  0xc02bc172 inflate_fixed:                               1168
> 
> Now what is interesting is these functions currently run with a 4KiB 
> stack on every bootup.  So unless they have callers with a
> significant stack footprint things are fine.

The longest call chain for these functions eats roughly 3.2k on i386
with allyesconfig.  Measured with a statical code checker, not tested.

Jörn

-- 
Simplicity is prerequisite for reliability.
-- Edsger W. Dijkstra
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/