[prev in list] [next in list] [prev in thread] [next in thread] 

List:       eros-arch
Subject:    Re: [eros-arch] Need for Asynchronous Non-Blocking Messages
From:       "Jonathan S. Shapiro" <shap () eros-os ! org>
Date:       2003-12-31 23:53:08
Message-ID: 1072914788.2974.18.camel () localhost ! localdomain
[Download RAW message or body]

On Wed, 2003-12-31 at 18:17, Ben Laurie wrote:
> Jonathan S. Shapiro wrote:
> 
> > On Wed, 2003-12-31 at 07:21, Ben Laurie wrote:
> > 
> >>>Actually, I can be waiting an arbitrary number of times, because once we
> >>>generalize this I can probably be in a capability invocation in lots of
> >>>contexts all at the same time. Activations begin to look pretty yucky in
> >>>this regard.
> >>
> >>Why would you want more than two?
> > 
> > 
> > Consider:
> > 
> > 1. Main context makes a capability call
> > 2. Activation context preempts main context, leading to user-mode
> > cswitch
> > 3. Second (or umpteenth) user-mode context makes a capability call...
> 
> Yeah, but don't do that. Interrupt the call in the top context and get 
> it to make the call. Hmm. I think I see where this all falls apart. The 
> problem is that the recipient of the original call is stuck until you 
> resume it, right?

Partly, but more importantly its a programming model breakdown.

_______________________________________________
eros-arch mailing list
eros-arch@mail.eros-os.org
http://www.eros-os.org/mailman/listinfo/eros-arch
[prev in list] [next in list] [prev in thread] [next in thread]