From: Imanpreet Arora <imanpreet@gmail.com>
To: Robert Love <rml@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question regarding thread_struct
Date: Tue, 8 Mar 2005 22:57:26 +0530 [thread overview]
Message-ID: <c26b959205030809271b8a5886@mail.gmail.com> (raw)
In-Reply-To: <1110302000.23923.14.camel@betsy.boston.ximian.com>
On Tue, 08 Mar 2005 12:13:20 -0500, Robert Love <rml@novell.com> wrote:
> On Tue, 2005-03-08 at 22:34 +0530, Imanpreet Arora wrote:
>
> > I am wondering if someone could provide information as to how
> > thread_struct is kept in memory. Robert Love mentions that it is kept
> > at the "lowest" kernel address in case of x86 based platform. Could
> > anyone answer these questions.
>
> Kernel _stack_ address for the given process.
>
> > a) When a stack is resized, is the thread_struct structure copied onto
> > a new place?
>
> This is the kernel stack, not any potential user-space stack. Kernel
> stacks are not resized.
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?
b) Or does it mean that a particular stack for a particular
process, can't be resized?
c) And for that matter how exactly do we define a kernel stack?
TIA
--
Imanpreet Singh Arora
next prev parent reply other threads:[~2005-03-08 17:28 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 [this message]
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
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=c26b959205030809271b8a5886@mail.gmail.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox