rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Paul Haahr <haahr@mv.us.adobe.com>
To: jeremy@sw.oz.au
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Interesting things from the Plan 9 rc manpage
Date: Tue, 27 Oct 1992 23:07:46 -0500	[thread overview]
Message-ID: <9210280407.AA15404@utopia.mv.us.adobe.com> (raw)

> A new process would share the
> namespace of its parent, including /env, so there's no work that needs
> to be done by any party.

yes, but a shell typically reads its entire environment on startup, and
all those readdir(), open(), read(), and close() operations can't be free.
on the other hand, if they don't cache the environment in the shell,
every reference to an environment variable has to do 3 system calls
(open, read, close), which is painful in my mind, but maybe rob's right
when he says you shouldn't worry about system call overhead.

thinking about it, they probably have to use the latter approach, because
otherwise you can't take advantage of the sharing of environments between
processes that plan 9 offers.

anyway, this is all idle speculation.


             reply	other threads:[~1992-10-28  4:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-10-28  4:07 Paul Haahr [this message]
1992-10-28  4:20 ` Jeremy Fitzhardinge
1992-10-28  4:27 ` Chris Siebenmann
  -- strict thread matches above, loose matches on Subject: below --
1992-10-28 15:27 Paul Haahr
1992-10-28  5:10 Chris Siebenmann
1992-10-28  3:14 Paul Haahr
1992-10-28  3:39 ` Chris Siebenmann
1992-10-28  4:00   ` Jeremy Fitzhardinge
1992-10-28  1:17 Byron Rakitzis
1992-10-28  1:57 ` noel
1992-10-28  1:59 ` noel
1992-10-28  5:59 ` James Matthew Farrow
1992-10-27 10:52 Chris Siebenmann
1992-10-27 16:08 ` Scott Schwartz

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=9210280407.AA15404@utopia.mv.us.adobe.com \
    --to=haahr@mv.us.adobe.com \
    --cc=jeremy@sw.oz.au \
    --cc=rc@hawkwind.utcs.toronto.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).