Objet : Developers list for StarPU
Archives de la liste
- From: Ankur Sharma <ankur.sharma@mailbox.tu-dresden.de>
- To: Samuel Thibault <samuel.thibault@ens-lyon.org>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] StarPU: Data flow between tasks
- Date: Wed, 1 Oct 2014 10:40:13 +0530
- 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>
Hi,
Thanks for the reply.
I actually want to access this information from the tasks so that I can write
them out to some file descriptor. In a format like
taskid
input1: taskid 1 -> datasize1 (dependency 1)
taskid 2 -> datasize2 (dependency 2)
…..
output: taskid3 -> datasize3
taskid4 -> datasize4
…
Sincere regards
Ankur Sharma
On 30 Sep 2014, at 18:51, Samuel Thibault <samuel.thibault@ens-lyon.org>
wrote:
> Ankur Sharma, le Thu 25 Sep 2014 08:53:28 +0200, a écrit :
>> Is it possible to measure the size of partitioned data allotted to each
>> task?
>
> Where do you want to get the information? Tasks themselves can access that
> information from the descriptor passed to the codelet. We haven't
> implemented
> getting the information on the generated task graph.
>
>> And is it possible to get the id of task that executes the cpu or cuda
>> implementation?
>
> From the codelet you can access the task by using
> starpu_task_get_current(), and
> thus its ID.
>
> Samuel
- Re: [Starpu-devel] StarPU: Data flow between tasks, Ankur Sharma, 01/10/2014
- Re: [Starpu-devel] StarPU: Data flow between tasks, Samuel Thibault, 01/10/2014
Archives gérées par MHonArc 2.6.19+.