From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 12 Jun 2010 07:51:35 -0400
To: 9fans@9fans.net
Message-ID: <f037be8b05322f2c60c0e3c2f30aa6a9@kw.quanstro.net>
In-Reply-To: <4C1351E6.8050109@bouyapop.org>
References: <4C1242CD.5020202@bouyapop.org>
	<AANLkTilQUS_JD8CWkcSJt_boJ1tBTG4i_xjZTfYfeyUl@mail.gmail.com>
	<f398e344c84e5946e0189ebb69638d57@kw.quanstro.net>
	<4C13311B.4050704@bouyapop.org> <4C1351E6.8050109@bouyapop.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] 9vx, kproc and *double sleep*
Topicbox-Message-UUID: 31ff1058-ead6-11e9-9d60-3106f5b1d025

> FYI, I've wondered if they had the same problem in go runtime because
> I suspected the code to be quite similar. And I think go team fixed the
> problem in ready() equivalent in go runtime, by adding a flag in Proc
> equivalent so the proc (G in go) is put back to the run queue ...

are you sure?  that big scheduler lock looks like it's doing
the job of splhi() to me.

- erik