Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] starpu_malloc() when StarPU is not initialized yet (or has been shut down)

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] starpu_malloc() when StarPU is not initialized yet (or has been shut down)


Chronologique Discussions 
  • From: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • To: Benoît Lizé <benoit.lize@gmail.com>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] starpu_malloc() when StarPU is not initialized yet (or has been shut down)
  • Date: Fri, 15 Mar 2013 00:50:22 +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>

Hello,

Benoît Lizé, le Thu 14 Mar 2013 11:25:54 +0100, a écrit :
> I would like to use starpu_malloc() instead of malloc(). However, reading
> the
> code in src/datawizard/malloc.c, it is not clear to me whether it is safe to
> call starpu_malloc() outside of starpu_init()/shutdown(),

It is not: starpu_malloc is meant to allocate pinned memory. For
most drivers (CUDA/OpenCL), this can only be done once the driver is
initialized, or worse, done inside the driver thread.

> and the overhead of starpu_malloc() compared to malloc() is not clear
> either.

When using CUDA or OpenCL, you have to count typically at least 10µs for
the allocation.

Samuel





Archives gérées par MHonArc 2.6.19+.

Haut de le page