From: erik quanstrom <quanstro@coraid.com>
To: rsc@swtch.com, 9fans@cse.psu.edu
Subject: Re: [9fans] wait hang
Date: Mon, 18 Dec 2006 15:00:51 -0500 [thread overview]
Message-ID: <0fee984c7b0eb63ea4f0ff13c7945c2c@coraid.com> (raw)
On Mon Dec 18 14:27:31 EST 2006, rsc@swtch.com wrote:
> I'm not really convinced this part of rc ever worked right to
> begin with, so this is no big loss.
you're right. this feature of rc doesn't work as expected. and your example
illustrates this well. for example if we try 20 wait records instead of 128:
; sleep 1000000 &
; pids=()
; for(i in `{seq 20}){
echo foo >/dev/null &
pids=($pids $apid)
}
; for(p in $pids){
echo $p
wait $p
}
4627
[hang]
since 20 is much less than 128, this can't be the kernel. i think the
problem is in the discarded wait messages here: rc/plan9.c/^Waitfor
int
Waitfor(int pid, int)
{
thread *p;
Waitmsg *w;
char errbuf[ERRMAX];
while((w = wait()) != nil){
if(w->pid==pid){
setstatus(w->msg);
free(w);
return 0;
}
for(p = runq->ret;p;p = p->ret)
if(p->pid==w->pid){
p->pid=-1;
strcpy(p->status, w->msg);
}
free(w);
}
errstr(errbuf, sizeof errbuf);
if(strcmp(errbuf, "interrupted")==0) return -1;
return 0;
}
byron's rc solves this problem by maintaining it's own waitlist in $apids.
; for(i in 1 2 3 4) { echo fu>/dev/null&}
31427
31428
31429
31430
; echo $apids
31427 31428 31429 31430
; echo $apids
31427 31428 31429 31430
; wait $apids(1)
; echo $apids
31428 31429 31430
; wait $apids(3)
; echo $apids
; wait 31428
;
i would think the right way to go may be to either remove
"wait $pid" from rc's vocabulary or do something like byron's rc.
- erik
next reply other threads:[~2006-12-18 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 20:00 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-20 3:55 erik quanstrom
2006-12-18 20:45 erik quanstrom
[not found] <db450a2ec40aeb8284b66f00407cb1cb@coraid.com>
2006-12-18 20:06 ` Russ Cox
2006-12-18 16:01 erik quanstrom
2006-12-18 16:40 ` Russ Cox
2006-12-18 19:05 ` erik quanstrom
2006-12-18 19:23 ` Russ Cox
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=0fee984c7b0eb63ea4f0ff13c7945c2c@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).