On Wed, 9 Mar 2005, Coywolf Qi Hunt wrote: > On Tue, 08 Mar 2005 12:28:42 -0500, Robert Love <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-03-08 at 22:57 +0530, Imanpreet Arora wrote: > > > > > This has been a doubt for a couple of days, and I am wondering if this > > > one could also be cleared. When you say kernel stack, can't be resized > > > > > > > > > a) Does it mean that the _whole_ of the kernel is restricted to > > > that 8K or 16K of memory? > > > > Actually, 4K or 8K these days for x86. But, no, it means that EACH > > PROCESS is constrained to the kernel stack. The stacks are per-process. > > The kernel never "runs on its own" -- it is always in the context of a > > process (which has its own kernel stack) or an interrupt handler (which > > either shares the previous process's stack or has its own stack, > > depending on CONFIG_IRQSTACKS). > > > CONFIG_IRQSTACKS seems only on ppc64. Is it good to add for other archs too?
i386 and x86_64 also have IRQ stacks - 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/
