Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] [starpu_matrix_filter_block: obtain block sizes, asynchronous interface]

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] [starpu_matrix_filter_block: obtain block sizes, asynchronous interface]


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Maksims Abalenkovs <m.abalenkovs@manchester.ac.uk>
  • Cc: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] [starpu_matrix_filter_block: obtain block sizes, asynchronous interface]
  • Date: Fri, 8 Dec 2017 12:03:16 +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,

Maksims Abalenkovs, on ven. 24 nov. 2017 17:26:07 +0000, wrote:
> 1) When I partition the data automatically using the
> “starpu_matrix_filter_block”, is there a way to obtain the block sizes via
> the
> StarPU API?

You mean, from outside the codelet function?
You can use starpu_data_get_interface_on_node with STARPU_MAIN_RAM, and
then use the usual STARPU_MATRIX_* macros to access sizes etc.

> 2) Do I understand correctly, that when I use asynchronous interface, i.e.
> plan
> and submit data partition via StarPU routines, there is no way to iterate
> via
> the blocks using “starpu_data_get_nb_children” and “starpu_data_get_child”
> from
> the Basic API ([2]http://starpu.gforge.inria.fr/doc/html/
> group__API__Data__Partition.html)?

Indeed, these are intended for synchronous partitioning. In
the asynchronous case, the subdata handles are returned by the
starpu_data_partition_plan call itself.

Samuel



  • Re: [Starpu-devel] [starpu_matrix_filter_block: obtain block sizes, asynchronous interface], Samuel Thibault, 08/12/2017

Archives gérées par MHonArc 2.6.19+.

Haut de le page