From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: James Simmons <jsimmons@edgeglobal.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, Linux MM <linux-mm@kvack.org>
Subject: Re: page faults
Date: Fri, 22 Oct 1999 11:15:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.991022111304.11326A-100000@kanga.kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9910221054550.23698-100000@imperial.edgeglobal.com>
On Fri, 22 Oct 1999, James Simmons wrote:
> Thank you for that answer. I remember you told me that threads under linux
> is defined as two processes sharing the same memory. So when a minor
> page fault happens by anyone one process will both process page tables get
> updated? Or does the other process will have a minor page itself
> independent of the other process?
Threads share the same page tables, hence the same memory. The other task
might end up with a minor fault, but after it aquires the semaphore, it
will discover the pte is already freshly faulted in.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-10-22 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 16:31 James Simmons
1999-10-21 19:40 ` Benjamin C.R. LaHaise
1999-10-22 0:47 ` Wang Yong
1999-10-22 13:06 ` Stephen C. Tweedie
1999-10-22 14:59 ` James Simmons
1999-10-22 15:15 ` Benjamin C.R. LaHaise [this message]
1999-10-22 17:35 ` Stephen C. Tweedie
1999-10-22 23:31 ` James Simmons
1999-10-24 17:15 ` Eric W. Biederman
1999-10-25 17:27 ` William J. Earl
1999-10-26 13:50 ` Marcus Sundberg
1999-10-26 14:00 ` Eric W. Biederman
1999-10-26 15:11 ` James Simmons
1999-10-26 18:04 ` William J. Earl
1999-10-26 9:05 ` Ralf Baechle
1999-10-29 14:52 ` James Simmons
1999-11-01 11:57 ` Stephen C. Tweedie
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=Pine.LNX.3.96.991022111304.11326A-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=jsimmons@edgeglobal.com \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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