Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] StarPU and MKL 11 (Intel Composer XE 2013)

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] StarPU and MKL 11 (Intel Composer XE 2013)


Chronologique Discussions 
  • From: Nathalie Furmento <nathalie.furmento@labri.fr>
  • To: Benoît Lizé <benoit.lize@gmail.com>
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] StarPU and MKL 11 (Intel Composer XE 2013)
  • Date: Tue, 18 Jun 2013 09:49:20 +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>

Thanks Benoit for your feedback.

I added your explanation in the documentation.

Cheers,

Nathalie

On Jun 17, 17:54, Benoît Lizé wrote:
> Hello,
>
> I recently talked off-list with some of you about some issues with MKL 11
> and StarPU.
> I'm using StarPU (1.1rc1 and 1.0.5) on Linux with MKL, using 1 thread for
> MKL and doing all the parallelism using StarPU (no multithreaded tasks),
> setting MKL_NUM_THREADS to 1.
> The threaded MKL library is used, with iomp5.
>
> Using this configuration, StarPU used only 1 core, no matter the value of
> STARPU_NCPU. Samuel mentionned that it looked like a thread pinning issue
> with MKL.
>
> I think I've found the solution: setting KMP_AFFINITY to disabled (
> http://software.intel
> .com/sites/products/documentation/studio/composer/en-us/2011Update/compiler_c/
> optaps/common/optaps_openmp_thread_affinity.htm). I wanted to share this
> workaround here.
>
> --
> Benoit Lize

> _______________________________________________
> Starpu-devel mailing list
> Starpu-devel@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/starpu-devel





Archives gérées par MHonArc 2.6.19+.

Haut de le page