Re: [Starpu-devel] [LU factorisation: gdb debug output]

[Samuel Thibault <samuel.thibault@inria.fr>]

Hello,

Maxim Abalenkov, on mer. 03 janv. 2018 20:03:10 +0100, wrote:
> a) What is the purpose of enforcing task execution on the home node? Is it
> always necessary, when I use the STARPU_DATA_MODE_ARRAY in
> “starpu_task_insert"? Please consider the code snippet I took from the
> “fmultiple_manual.c”:
> 
>     // Enforce task execution on home node (STARPU_MAIN_RAM)
>     core_starpu_codelet_zgetrf_pnl.specific_nodes = 1;
> 
>     for (int i = 0; i < STARPU_NMAXBUFS; i++) {
>         core_starpu_codelet_zgetrf_pnl.nodes[i] = STARPU_MAIN_RAM;
>     }

See the comment in the corresponding codelet function:

       /* This doesn't need to do anything, it's simply used to make coherency
        * between the two views, by simply running on the home node of the
        * data, thus getting back all data pieces there.  */

It's just a matter of collecting all pieces together on the same memory
node.

> b) Can you please direct me to an example(s) of using StarPU subtasks (tasks
> submitted by other tasks)?

I have to say I don't remember such kind of example. The problem is
that doing this kind of thing raises a lot of issues. Notably, if you
keep the default sequential consistency on data, the subtasks will
automatically be made to depend on the last submitted tasks which work
on the same data. I guess that's not what you want. Perhaps Terry and
Nathalie will have better answers with the addition of the notion of
bubble. At any rate, we need to know much better what exact semantic you
want from your subtasks, to determine what could suit your needs.

Samuel