From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rfork(), getss() etc etc
Date: Sat, 2 Sep 2000 22:51:22 -0400 [thread overview]
Message-ID: <20000903025123.1915.qmail@g.bio.cse.psu.edu> (raw)
In-Reply-To: Message from Alexander Viro <viro@math.psu.edu> of "Sat, 02 Sep 2000 06:52:57 EDT." <Pine.GSO.4.10.10009020555201.9425-100000@weyl.math.psu.edu>
| You will not notice the effect simply benshmarking schedule(),
| but you will get big slowdown spread over the userland. It's not a pure
| theory - effect is quite visible.
Just out of curiosity, do any real linux programs use clone or pthreads
or whatever? Say what you like about rfork, but lots of real programs
make good use of it.
next prev parent reply other threads:[~2000-09-03 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-02 9:49 nigel
2000-09-02 10:52 ` Alexander Viro
2000-09-03 2:51 ` Scott Schwartz [this message]
2000-09-03 3:03 ` Boyd Roberts
2000-09-05 5:32 ` Erik Theisen
-- strict thread matches above, loose matches on Subject: below --
2000-09-02 7:50 nigel
2000-09-02 8:57 ` Alexander Viro
2000-09-02 9:31 ` Alexander Viro
2000-09-02 9:39 ` Alexander Viro
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=20000903025123.1915.qmail@g.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).