9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Roman V. Shaposhnik" <rvs@sun.com>
To: erik quanstrom <quanstro@quanstro.net>
Cc: 9fans@9fans.net
Subject: Re: [9fans] Calling vac from C
Date: Tue, 24 Feb 2009 09:17:18 -0800	[thread overview]
Message-ID: <1235495838.28500.577.camel@goose.sun.com> (raw)
In-Reply-To: <c9aea65e7f058933edc0a22e931ea675@quanstro.net>

On Tue, 2009-02-24 at 12:01 -0500, erik quanstrom wrote:
> data would be helpful.

Indeed! Personally, I'm not old enough to have lived
through most of these wars to tell a story.

> nobody here has shown any version
> of solaris to be slow forking, much less that it is slow
> forking because of accounting.  my dimly-remembered
> data support the conclusion that the now-ancient 670mp
> had a poor mmu, not that solaris was good or bad.

Here's my understanding of Sun's oral history: MMU
was, indeed, an issue. But somehow it wasn't really
about shared objects at the time, but a simple COW
machinery being slow. Thus vfrok() was born as an attempt
to avoid *any* MMU work.

Could it also be the birth of "Solaris's fork() being
slow myth"?

Thanks,
Roman.




       reply	other threads:[~2009-02-24 17:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c9aea65e7f058933edc0a22e931ea675@quanstro.net>
2009-02-24 17:17 ` Roman V. Shaposhnik [this message]
2009-02-24 17:01 erik quanstrom
     [not found] <ac072e66c823fd6d649593efec9e221b@quanstro.net>
2009-02-24 16:32 ` Roman V. Shaposhnik
  -- strict thread matches above, loose matches on Subject: below --
2009-02-24 16:22 erik quanstrom
2009-02-24 15:54 erik quanstrom
2009-02-24 16:15 ` Roman V. Shaposhnik
2009-02-19  9:53 anooop.anooop
2009-02-19 12:55 ` erik quanstrom
2009-02-20  9:53 ` anooop.anooop
2009-02-20 15:41   ` erik quanstrom
2009-02-20 16:17     ` Uriel
2009-02-20 16:47       ` erik quanstrom
2009-02-24  6:10         ` Ben Calvert

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=1235495838.28500.577.camel@goose.sun.com \
    --to=rvs@sun.com \
    --cc=9fans@9fans.net \
    --cc=quanstro@quanstro.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).