From: Sam Steingold <sds@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Andreas Schwab <schwab@suse.de>,
Chong Yidong <cyd@stupidchicken.com>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Change in process.c
Date: Wed, 28 Mar 2007 10:02:39 -0400 [thread overview]
Message-ID: <460A757F.3000308@gnu.org> (raw)
In-Reply-To: <17929.38544.280560.227806@farnswood.snap.net.nz>
Nick Roberts wrote:
> > /* For some reason, this sleep() prevents Emacs from sending
> > loadavg to 5-8(!) for ~10 seconds.
> > See http://thread.gmane.org/gmane.emacs.devel/67722 or
> > http://www.google.com/search?q=busyloop+in+sigchld_handler */
>
> Links that might disappear, and searches whose results will change, as comments
> doesn't seem a good idea.
the link will not disappear any more than a "gnu.org" link will.
if you have a better link, please add it.
> Can't the reason for the change be summarised in situ?
it is summarized: "or some reason, this sleep() prevents Emacs from
sending loadavg to 5-8(!) for ~10 seconds".
40 messages of various conjectures, claims, counterclaims, rebuttals &c
are long but of dubious value inside the source code.
next prev parent reply other threads:[~2007-03-28 14:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 23:13 Change in process.c Richard Stallman
2007-03-27 3:06 ` Sam Steingold
2007-03-27 9:55 ` Andreas Schwab
2007-03-27 10:33 ` Nick Roberts
2007-03-27 16:43 ` Richard Stallman
2007-03-27 21:16 ` Chong Yidong
2007-03-27 22:11 ` Nick Roberts
2007-03-28 14:02 ` Sam Steingold [this message]
2007-03-28 21:09 ` Nick Roberts
2007-03-28 13:55 ` Sam Steingold
2007-03-28 14:13 ` Andreas Schwab
2007-03-28 15:25 ` Sam Steingold
2007-03-28 19:08 ` Jan Djärv
2007-03-28 20:57 ` Kim F. Storm
2007-03-29 6:12 ` Jan Djärv
2007-03-29 21:25 ` Kim F. Storm
2007-03-28 15:11 ` Chong Yidong
2007-03-28 16:09 ` Richard Stallman
2007-03-29 13:57 ` Randal L. Schwartz
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=460A757F.3000308@gnu.org \
--to=sds@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).