From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] what am i missing
Date: Wed, 25 Apr 2012 17:10:15 -0400 [thread overview]
Message-ID: <43753423e1d13c42e5a6d0feb69f52d9@brasstown.quanstro.net> (raw)
In-Reply-To: <CADSkJJURoTSsuNHWpHb6=yWvQh9-DpQ3h+nMxC=s0AdYUj-h_A@mail.gmail.c>
On Wed Apr 25 17:01:18 EDT 2012, rsc@swtch.com wrote:
> On Wed, Apr 25, 2012 at 4:37 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> > On Wed Apr 25 16:15:27 EDT 2012, rsc@swtch.com wrote:
> >> This is not Linux. Each individual proc (thread) has its own
> >> set of children, so the only wait message that should arrive
> >
> > and yet the threadwaitchan() is shared among all threads in all
> > procs, no?
>
> Yes, of course, but I don't understand why that is relevant.
> We were talking about whether _schedexecwait should ever
> get a Waitmsg with w->pid != pid that is not okay to throw
> on the floor. Did you actually observe a problem using the
> thread library? If so, an actual test program would be great.
no, i was confused. there is no bug.
the reason i'm noting that everything gets tossed on the same
channel with disappointment is that the idea was to create pairs
of processes sources (procrfork/procexecl) and proc sinks
(wait; but that doesn't work) so the total number outstanding/rate/
processor use could be managed independently for each.
- erik
prev parent reply other threads:[~2012-04-25 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 19:46 erik quanstrom
2012-04-25 20:03 ` Russ Cox
[not found] ` <CADSkJJV_C6qrqDDXgRm0jPwRWoX2-YckOCf1bMati625Co5CMg@mail.gmail.c>
2012-04-25 20:06 ` erik quanstrom
2012-04-25 20:14 ` Russ Cox
[not found] ` <CADSkJJVeG7ZqCpnqVd0SvRhKmnWUrewX04kYVX-VTUb50Uemqw@mail.gmail.c>
2012-04-25 20:37 ` erik quanstrom
2012-04-25 21:00 ` Russ Cox
[not found] ` <CADSkJJURoTSsuNHWpHb6=yWvQh9-DpQ3h+nMxC=s0AdYUj-h_A@mail.gmail.c>
2012-04-25 21:10 ` erik quanstrom [this message]
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=43753423e1d13c42e5a6d0feb69f52d9@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).