From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Re: bug in aux/listen
Date: Tue, 16 Sep 1997 15:00:44 -0500 [thread overview]
Message-ID: <19970916200044.0Hf_REpx0DGaMyr1ao1zflU-a7y1GXpVUAIheZfRfBQ@z> (raw)
From: rob@plan9.bell-labs.com
>
>> saying that subsequent forks by the *parent*, if called with RFMEM,
>> will share data and bss between children of the *parent*. Subsequent
>> forks of the children are not affected unless they too do a RFMEM.
>
>The flag gets set on the segment, not the process. Any process created
>with that segment mapped will see the same segment.
Let me look again. Hmmm... Ah, there it is, hiding at the top...
switch(s->type&SG_TYPE) {
case SG_TEXT:
case SG_SHARED:
case SG_PHYSICAL:
case SG_SHDATA:
incref(s);
return s;
Ok, once it is marked shared any new fork, no matter what the share
flag is set to, will get the *same* segment. Wow, you need to be
careful with RFMEM!!!
I stand corrected.
David Butler
next reply other threads:[~1997-09-16 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-16 20:00 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-16 19:25 rob
1997-09-16 18:57 G.David
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=19970916200044.0Hf_REpx0DGaMyr1ao1zflU-a7y1GXpVUAIheZfRfBQ@z \
--to=9fans@9fans.net \
/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).