From: jigsaw@gmail.com (jigsaw)
Subject: [TUHS] Reading UNIX V6: Does eash process has its own user structure, or all the processes share one copy of it?
Date: Tue, 3 Oct 2006 13:35:11 +0300 [thread overview]
Message-ID: <2051ec920610030335y2ceecac9v8980cd14c1d91b20@mail.gmail.com> (raw)
In-Reply-To: <1159867990.4933.384.camel@papa>
hi Hellwig,
Thank you. Now the first 2 questions are cleared.
I guess the answer to 3rd question is buried in m40.s.....I will check it out.
Thanks again.
Regards,
Qinglai
On 10/3/06, Hellwig Geisse <Hellwig.Geisse at mni.fh-giessen.de> wrote:
> On Tue, 2006-10-03 at 12:05 +0300, jigsaw wrote:
> > First, I doubt whether all processes share one "u" or each process has
> > its own "u".
>
> Every process has its own u-area.
> They have all at the same virtual kernel address,
> but live in different physical locations.
>
> > So isn't it saying that there's only one "u" in the core memory?
>
> No. The running process' u-area is mapped into
> the virtual address space before executing any
> instructions of the process.
>
> Hellwig
>
>
next prev parent reply other threads:[~2006-10-03 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 9:05 jigsaw
2006-10-03 9:33 ` Hellwig Geisse
2006-10-03 10:35 ` jigsaw [this message]
[not found] ` <74f31973c70413b149f1e383bf47dae0@coraid.com>
2006-10-03 18:23 ` [TUHS] Reading UNIX V6: Does eash process has its own user jigsaw
2006-10-03 19:40 ` Brantley Coile
2006-10-03 12:58 [TUHS] Reading UNIX V6: Does eash process has its own user structure, or all the processes share one copy of it? Wolfgang Helbig
2006-10-03 20:26 ` jigsaw
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=2051ec920610030335y2ceecac9v8980cd14c1d91b20@mail.gmail.com \
--to=jigsaw@gmail.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;
as well as URLs for NNTP newsgroup(s).