Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Implementation question regarding output type

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Implementation question regarding output type


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Johan Mazel <johan.mazel@gmail.com>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Implementation question regarding output type
  • Date: Fri, 20 Dec 2019 17:19:37 +0100
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel/>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
  • Organization: I am not organized

Hello,

Johan Mazel, le jeu. 19 déc. 2019 14:02:11 +0100, a ecrit:
> This is quite slow because I guess that StarPU has to transfer back all the
> result vectors to the RAM.

Yes.

> I identified two possible solutions :
> * Define a new data interface ([1]http://starpu.gforge.inria.fr/doc/html/

I don't think this will be needed

> * Use the CSR data interface.

That seems overkill :)

> Which one of these two methods looks do you think is the most appropriate
> for
> my use case? Do you know any examples that use a similar method?

I believe you can just use vectors, by reallocating it during the task.
I have now added a "Changing the size of a data" section in the StarPU
handbook. Basically the bits are shown in the kernel() function in
tests/datawizard/variable_size.c: you just reallocate the data buffer
and fix the size. When StarPU brings back the data to the main memory,
it will only have to transfer that piece.

Samuel




Archives gérées par MHonArc 2.6.19+.

Haut de le page