public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Scott Long <smlong@teleport.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Threads and the LDT (Intel-specific)?
Date: Sun, 10 Jun 2001 15:40:59 -0300	[thread overview]
Message-ID: <200106101941.PAA00669@karaya.com> (raw)
In-Reply-To: Your message of "Sun, 10 Jun 2001 11:53:29 PDT." <01061011532900.01126@abacus>

smlong@teleport.com said:
> I'm trying to do something a bit unorthodox: I want to share the
> address space between threads, but I want a certain region of the
> address space to be writeable only for a particular thread -- for all
> other threads this region is read-only. 

UML does this in a somewhat portable (but strange) way.  Threads don't share 
address spaces, as far as the OS is concerned, but the areas where the 
executable is mapped in are copied to a file, those areas are mapped out, and 
the files mapped shared in their place.  This happens once, in the first 
thread, and all subsequent threads get the executable mapped shared 
automatically, even though they are separate processes and separate address 
spaces from the point of view of the kernel.

So, once this is set up, a thread just makes an area read-write (or readonly) 
and that mapping is private.

				Jeff



  reply	other threads:[~2001-06-10 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-10 18:53 Threads and the LDT (Intel-specific)? Scott Long
2001-06-10 18:40 ` Jeff Dike [this message]
     [not found] <01061011532900.01126@abacus.suse.lists.linux.kernel>
2001-06-13  9:15 ` Andi Kleen

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=200106101941.PAA00669@karaya.com \
    --to=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smlong@teleport.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