Objet : Developers list for StarPU
Archives de la liste
- From: Sylvain HENRY <sylvain.henry@inria.fr>
- To: "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>, augonnet@nvidia.com
- Subject: [Starpu-devel] OpenCL backend on CPU
- Date: Thu, 08 Sep 2011 15:05:00 +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>
Hi,
I'm using StarPU's OpenCL backend on CPU (using AMD's or Intel's implementation). The problem is that StarPU considers the CPU device as remote and thus performs asynchronous data transfers while it could work on data in-place.
With AMD's OpenCL implementation, asynchronous data transfers are not performed, at least until a blocking command (clWaitForEvents or clFinish) is called. With Intel it works fine but an unnecessary data copy occurs.
I would like to avoid this data copy. What would be the best way to implement this in StarPU?
Cheers
Sylvain
- [Starpu-devel] OpenCL backend on CPU, Sylvain HENRY, 08/09/2011
- <Suite(s) possible(s)>
- Re: [Starpu-devel] OpenCL backend on CPU, Samuel Thibault, 08/09/2011
Archives gérées par MHonArc 2.6.19+.