From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: [9fans] Re: patch/list sorry/nbroken-8
Date: Thu, 30 Mar 2006 00:47:50 +0200 [thread overview]
Message-ID: <c9b8386f82b75be6378776d02fe355f5@cat-v.org> (raw)
In-Reply-To: <e644f5197ca0a9d59548f0fcf0c49f52@plan9.bell-labs.com>
> d-rwxrwxr-x M 430 uriel sys 0 Mar 29 17:38 sorry/nbroken-8
> from uriel@cat-v.org
> /sys/src/9/port/proc.c
> Upper NBROKEN to 8 to avoid lossing broken procs in long-running cpu servers.
>
> Wed Mar 29 17:37:57 EST 2006 rsc
> This is an arbitrary choice. Why not 16?
> If you want to make it different in your own systems go ahead,
> but I don't see the point here.
>
> The default is fine as it is.
IMHO the default is way too low (and undocumented as far as I can
tell.) 8 is also arbitrary, but seems like a much more reasonable
value in most cases, going over 4 broken processes is not hard if you
have bad luck and a long running box, going over 8 broken processes is
considerably harder, like all magic numbers, all matter of judgement
and experimentation.
Note that others have also reported broken procs 'vanishing', probably
because they didn't know there was a limit and that the limit was so
low.
uriel
next parent reply other threads:[~2006-03-29 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e644f5197ca0a9d59548f0fcf0c49f52@plan9.bell-labs.com>
2006-03-29 22:47 ` uriel [this message]
2006-03-29 22:57 ` Steve Simon
2006-03-29 23:01 ` uriel
2006-03-29 23:28 ` Skip Tavakkolian
2006-03-29 23:37 ` Russ Cox
2006-03-30 1:56 ` geoff
2006-03-30 10:52 ` Richard Miller
2006-03-30 12:15 Fco. J. Ballesteros
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=c9b8386f82b75be6378776d02fe355f5@cat-v.org \
--to=uriel@cat-v.org \
--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).