Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] Questions around StarPU

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] Questions around StarPU


Chronologique Discussions 
  • From: Ronan Keryell <Ronan.Keryell@hpc-project.com>
  • To: Samuel Thibault <samuel.thibault@ens-lyon.org>
  • Cc: Stephanie Even <Stephanie.Even@hpc-project.com>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] Questions around StarPU
  • Date: Wed, 21 Sep 2011 14:36:15 -0700
  • 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>

>>>>> On Wed, 21 Sep 2011 19:10:51 +0200, Samuel Thibault
>>>>> <samuel.thibault@ens-lyon.org> said:
Samuel> If the user uses malloc before registering, the memory won't
Samuel> be pinned. The user needs to either call cudaMalloc, or use
Samuel> starpu_malloc() to get pinned memory (the latter will always
Samuel> work whether CUDA is available or not).

I'm curious about how it can work if you use CUDA over StarPU over
MPI for example...

It sounds to me that this "pinned" allocation has to be done then at the
StarPU proxy on the remote host?

Idem in OpenCL with the equivalent buffer creation options?

Thanks,
--
Ronan KERYELL |\/ Phone: +1 408 844 HPC0
HPC Project, Inc. |/) Cell: +33 613 143 766
5201 Great America Parkway #3241 K Ronan.Keryell@hpc-project.com
Santa Clara, CA 95054 |\ skype:keryell
USA | \ http://hpc-project.com





Archives gérées par MHonArc 2.6.19+.

Haut de le page