On Wed Apr 25 17:01:18 EDT 2012, [email protected] wrote: > On Wed, Apr 25, 2012 at 4:37 PM, erik quanstrom <[email protected]> wrote: > > On Wed Apr 25 16:15:27 EDT 2012, [email protected] 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
