[coyotos-dev] Sleep for interval

[Jonathan S. Shapiro]

On Sun, 2007-09-30 at 19:51 -0700, Charles Landau wrote:

> 2. If the returnee exits the receiving state, the resume key held by 
> the sleep object (in this case the kernel) becomes void, and no 
> wakeup occurs.

What storage does the kernel use to hold this resume capability?

> 3. The first wakeup invokes its resume key, which voids the resume 
> keys held by all the other sleeps.

Okay. That makes sense.

> I should disclose that at the moment, CapROS sleep suffers from the 
> misfeature I'm arguing against here. I intend to fix it, and at this 
> point I'm not aware of any obstacles to doing so, but maybe I just 
> haven't thought about it enough.

Well, for my part I have never liked the "block the caller" design
either. I did it because I couldn't figure out how to make the kernel
storage requirements work doing it your way. It is very possible that I
simply didn't think about it hard enough.

That being said, the reliance on resume keys evaporating won't work in
Coyotos, because we don't have resume keys. The corresponding entry
capabilities will become invalid only if the application is using the
"payload match" mechanism.

shap
-- 
Jonathan S. Shapiro
Managing Director
The EROS Group, LLC
www.coyotos.org, www.eros-os.org