From: "Thomas Bushnell, BSG" <tb+usenet@becket.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] authorization schemes (was CORBA)
Date: Mon, 8 Oct 2001 09:36:28 +0000 [thread overview]
Message-ID: <87lmiph421.fsf@becket.becket.net> (raw)
In-Reply-To: <20011001121653.3DC8F19A3D@mail.cse.psu.edu>
rob@plan9.bell-labs.com (rob pike) writes:
> Copy on write is easy on a uniprocessor. It gets nastier on
> a multiprocessor. Our solution was to switch to copy on
> reference on the MP.
It can be a nice strategy to use copy-on-write to hold things like
libraries shared by many processes. Then if one process happens to
get a breakpoint, the debugger can just write the library page in that
process's image, and the copy-on-write does the right thing. Normal
processes all happily share.
Doesn't that break if you use copy on reference?
Perhaps I'm misunderstanding you...
next prev parent reply other threads:[~2001-10-08 9:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 12:16 rob pike
2001-10-08 9:36 ` Thomas Bushnell, BSG [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 11:11 forsyth
2001-10-01 12:24 rob pike
2001-10-01 12:48 ` Boyd Roberts
2001-10-01 11:00 forsyth
2001-09-26 18:08 presotto
2001-09-26 17:44 presotto
2001-09-26 17:59 ` Boyd Roberts
2001-09-27 11:04 ` Douglas A. Gwyn
2001-09-26 17:39 Scott Schwartz
2001-09-26 17:55 ` Boyd Roberts
2001-09-26 19:15 ` Mike Haertel
2001-09-26 21:57 ` Boyd Roberts
2001-09-27 11:05 ` Douglas A. Gwyn
2001-09-27 11:34 ` Boyd Roberts
2001-10-01 9:49 ` Douglas A. Gwyn
2001-10-01 10:32 ` Boyd Roberts
2001-10-01 10:35 ` David Lukes
2001-10-01 14:29 ` Ronald G Minnich
2001-10-02 1:02 ` Boyd Roberts
2001-10-02 3:09 ` Ronald G Minnich
2001-10-02 8:14 ` Boyd Roberts
2001-10-04 9:11 ` Douglas A. Gwyn
2001-10-04 9:28 ` Boyd Roberts
2001-10-04 10:28 ` davel
2001-10-04 10:34 ` Boyd Roberts
2001-10-05 8:43 ` Douglas A. Gwyn
2001-10-02 9:05 ` David Lukes
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=87lmiph421.fsf@becket.becket.net \
--to=tb+usenet@becket.net \
--cc=9fans@cse.psu.edu \
/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).