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 08:32:32 -0800 [thread overview]
Message-ID: <1235493152.28500.536.camel@goose.sun.com> (raw)
In-Reply-To: <ac072e66c823fd6d649593efec9e221b@quanstro.net>
On Tue, 2009-02-24 at 11:22 -0500, erik quanstrom wrote:
> > > cfork is ~525 lines long and seems to take the curious tack of
> > > forking all the lwps associated with a process.
> >
> > that would be forkall(), not fork1()/fork()
>
> my mistake. i assumed that since isfork1 was
> a flag, that it was not the normal path through
> the code. silly me.
>
> so where's the mythical accounting?
It could have been the "old" accounting. Solaris 10
changed a lot of that and made things like microstate
accounting on by default, thus, possibly eliminating
the kind of bottlenecks the instructor was referring
to. More on that here:
http://blogs.sun.com/eschrock/entry/microstate_accounting_in_solaris_10
Thanks,
Roman.
next parent reply other threads:[~2009-02-24 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ac072e66c823fd6d649593efec9e221b@quanstro.net>
2009-02-24 16:32 ` Roman V. Shaposhnik [this message]
[not found] <c9aea65e7f058933edc0a22e931ea675@quanstro.net>
2009-02-24 17:17 ` Roman V. Shaposhnik
2009-02-24 17:01 erik quanstrom
-- 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=1235493152.28500.536.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).