From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Robert Love <rml@novell.com>
Cc: Imanpreet Arora <imanpreet@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Question regarding thread_struct
Date: Wed, 9 Mar 2005 02:14:18 +0800 [thread overview]
Message-ID: <2cd57c9005030810144cfc0b@mail.gmail.com> (raw)
In-Reply-To: <1110302922.28921.3.camel@betsy.boston.ximian.com>
On Tue, 08 Mar 2005 12:28:42 -0500, Robert Love <rml@novell.com> 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?
Regards
--
Coywolf Qi Hunt
Homepage http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-03-08 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 17:04 Question regarding thread_struct Imanpreet Arora
2005-03-08 17:13 ` Robert Love
2005-03-08 17:27 ` Imanpreet Arora
2005-03-08 17:28 ` Robert Love
2005-03-08 17:55 ` Imanpreet Arora
2005-03-08 17:58 ` Robert Love
2005-03-08 18:14 ` Coywolf Qi Hunt [this message]
2005-03-08 18:12 ` Robert Love
2005-03-08 18:27 ` Zwane Mwaikambo
2005-03-08 17:57 ` linux-os
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=2cd57c9005030810144cfc0b@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=imanpreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.