Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: Ronan Keryell <Ronan.Keryell@hpc-project.com>
- 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 23:37:45 +0200
- 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>
Ronan Keryell, le Wed 21 Sep 2011 14:36:15 -0700, a écrit :
> >>>>> 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?
What do you call "StarPU proxy"? Whenever StarPU allocates a buffer for
some handle, it uses pinned allocation.
> Idem in OpenCL with the equivalent buffer creation options?
Yes.
Samuel
- Re: [Starpu-devel] Questions around StarPU, Samuel Thibault, 21/09/2011
- Re: [Starpu-devel] Questions around StarPU, Ronan Keryell, 21/09/2011
- Re: [Starpu-devel] Questions around StarPU, Samuel Thibault, 21/09/2011
- Re: [Starpu-devel] Questions around StarPU, Ronan Keryell, 21/09/2011
Archives gérées par MHonArc 2.6.19+.