Re: [Starpu-devel] Unexpected behavior - Not making task ready when they could be

[Samuel Thibault <samuel.thibault@ens-lyon.org>]

Samuel Thibault, le Fri 13 Feb 2015 16:39:55 +0100, a écrit :
> I remember very well it mentioned while Cédric developped StarPU, and
> we preferred to use a simple solution at the time: StarPU just uses a
> ticket-based approach, which thus can not take COMMUTE into account.

I forgot a detail: we additionally sort handles by pointer value, to
avoid deadlocks. So the scenario I explained:

> A0 can start. Then A01 gets a ticket on H0, A02 gets a ticket on H0,
> etc. A1 can start. Then A10 gets a ticket on H1, A12 gets a ticket on
> H1, etc. 

is not exactly that: A10 will get a ticket on H0 actually. But that
doesn't change the scenario much, the same issue will happen.

Samuel