From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] closeproc slow
Date: Sun, 23 Jul 2006 08:34:58 -0800 [thread overview]
Message-ID: <858ebb6298e3121386c0507c15527835@swtch.com> (raw)
In-Reply-To: <839c4573978f1732e636f7651c96eb78@quanstro.net>
Your processes died a quick and painless death.
The closeproc helpers, called upon to clean up after
the battle, leave at a rate of one per five seconds.
I was trying to avoid repeatedly creating and deleting
processes if someone is killing procs frequently.
In that case, the right number of closeprocs will stick
around and get reused.
Russ
next prev parent reply other threads:[~2006-07-23 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 10:06 erik quanstrom
2006-07-23 16:34 ` Russ Cox [this message]
2006-07-23 15:23 ` erik quanstrom
2006-07-23 16:43 ` Russ Cox
2006-07-23 15:34 ` erik quanstrom
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=858ebb6298e3121386c0507c15527835@swtch.com \
--to=rsc@swtch.com \
--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).