With great care is right :) But seriously, work stealing is a huge undertaking in this model, and may not be feasible at all as far as I can tell. Every private heap object accessed by a thread has to be copied either to the shared heap or to the stealer's heap. This is the downside of not having one shared heap for everything. Of course there are huge upsides as well, but I don't see how work stealing could work efficiently. The only exception would be for a thread that hasn't started running at all, or has allocated very little.

On Tue, Sep 9, 2014 at 11:06 AM, Stephen Dolan <stephen.dolan@cl.cam.ac.uk> wrote:
On Tue, Sep 9, 2014 at 3:24 AM, Yotam Barnoy <yotambarnoy@gmail.com> wrote:
> I have another question about the runtime. I believe it was mentioned in the
> talk that there would be work-stealing between the domains. But how can we
> have any work-stealing when the fibers are integrated deeply inside the
> domains' local heaps?

With great care.

Stephen