Concurrency Proposal

[Brian Rice]

I'm jumping the gun a bit here, but Levi is an undergrad student who  
is trying to get academic sponsorship for some Slate work in this  
direction, so he may be able to work on this seriously.

I don't have much to directly comment on except that it'd be a  
benefit to get some discussion on the technical points so that we  
wind up with a good initial design and don't "code ourselves into a  
corner"; concurrent programming support can be a tricky issue in that  
it pervades assumptions about code and what it can do.

Also, there should be a relation kept in mind between this and the E- 
style work that was done before (mainly in src/lib/process.slate and  
src/lib/concurrency.slate), even if the relation is "replace most of  
it", although eventual-sends are a good idea regardless.

I will say that Scheme48 does offer some decent ideas on how to go  
about things portably, and I need to look at its continuation code  
since they use an array-based stack as well.

On Mar 8, 2006, at 8:58 AM, Levi Pearson wrote:

> Here's the design I've been working on for an implementation of low-
> level concurrency support in the vm.  Please let me know if you see
> any design flaws or find the description unclear in any aspect.  I
> hope to contribute to the implementation, but my time for hacking is
> limited so it'd be nice if others wanted to work on implementing it
> as well.
>
> This provides only the lowest-level of support for preemptive thread
> switching; lots of userspace code design is left to be done.

--
-Brian
http://tunes.org/~water/brice.vcf

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : /archives/slate/attachments/20060309/15c81515/PGP.pgp