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

Kenneth Parrish <[email protected]> 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.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Jörn Engel <[email protected]>

• References:
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Kenneth Parrish <[email protected]>

• Prev by Date: Re: [RFC] un petite hack: /proc/*/ctl
• Next by Date: kiobuf mechanism for SATA drivers
• Previous by thread: Re: [2.6 patch] i386: always use 4k stacks
• Next by thread: Re: [2.6 patch] i386: always use 4k stacks
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]