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

Stefan Rompf wrote:

Wrong. The probability that an interrupt happens just during the codepath with highest stack usage is very small. Anyway CONFIG_DEBUG_STACKOVERFLOW is not enabled in 2.6.14.4 i386 defconfig. Don't know about vendor kernel kernels though.

Well, the interrupts have their own stack (if using 4k stacks) so

the interrupt timing shouldn't matter.

Helge Hafting
-
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/

---

• References:
  • Re: [2.6 patch] i386: always use 4k stacks
    • From: Stefan Rompf <[email protected]>
  • Re: [2.6 patch] i386: always use 4k/4k stacks
    • From: Arjan van de Ven <[email protected]>
  • Re: [2.6 patch] i386: always use 4k/4k stacks
    • From: Stefan Rompf <[email protected]>

• Prev by Date: Re: [2.6 patch] i386: always use 4k stacks
• Next by Date: SPI core function names
• Previous by thread: Re: [2.6 patch] i386: always use 4k/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]