mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Love <rml@novell.com>
To: Imanpreet Arora <imanpreet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question regarding thread_struct
Date: Tue, 08 Mar 2005 12:13:20 -0500	[thread overview]
Message-ID: <1110302000.23923.14.camel@betsy.boston.ximian.com> (raw)
In-Reply-To: <c26b959205030809044364b923@mail.gmail.com>

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.

> b)	What is the advantage of this scheme as against a fixed "virtual-address"?

This is inside of the kernel, not in user-space.

> c)	Also could you kindly point the relevant files which do all this
> stuff "shed.c"(?)

See kernel/fork.c and alloc_thread_info() and friends in
<asm/thread_info.h>.

	Robert Love



  reply	other threads:[~2005-03-08 17:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 17:04 Imanpreet Arora
2005-03-08 17:13 ` Robert Love [this message]
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
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=1110302000.23923.14.camel@betsy.boston.ximian.com \
    --to=rml@novell.com \
    --cc=imanpreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®