[coyotos-dev] Blocking Sends

[Jonathan S. Shapiro]

For Mx1 threading this is a problem. No workaround is possible in
principle, because you only have 1 blockable thing. For MxN threading,
you have N blockable things.

The problem, fundamentally, is that you need something to hang on the
receiver stall queue, and the process cannot simultaneously hang there
and also be doing something else.

There are sleazy tricks that one could imagine using ReceiveQ's, but all
of them entail race conditions that can fail to achieve the real goal.

shap

On Wed, 2006-05-31 at 19:50 +0200, Neal H. Walfield wrote:
> At Wed, 31 May 2006 13:35:02 -0400,
> Jonathan S. Shapiro wrote:
> > 
> > It cannot be, because this would require a reverse notification on
> > unblock, and there simply isn't any good place to leave the necessary
> > data structure. The process blocks as a whole.
> 
> This is interesting as it sounds like it will make implementing a user
> level thread package quite difficult: anytime any user thread blocks,
> all thread block.  Do you see this as a problem?  Do you imagine a
> work around?
> 
> Thanks,
> Neal
> _______________________________________________
> coyotos-dev mailing list
> coyotos-dev at smtp.coyotos.org
> http://www.coyotos.org/mailman/listinfo/coyotos-dev