Accéder au contenu.
Menu Sympa

starpu-devel - [Starpu-devel] Combined workers and OpenMP code

Objet : Developers list for StarPU

Archives de la liste

[Starpu-devel] Combined workers and OpenMP code


Chronologique Discussions 
  • From: Keisuke Fukuda <fukuda@matsulab.is.titech.ac.jp>
  • To: starpu-devel@lists.gforge.inria.fr
  • Subject: [Starpu-devel] Combined workers and OpenMP code
  • Date: Wed, 25 Apr 2012 18:35:48 +0900
  • 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 all,

I'm working on StarPU's "combined workers" feature and have got some
questions.
I've wrote a very simple code, which is similar to
"example/openmp/vector_scal.c".
I put it at https://gist.github.com/2488259 .

When I run the code on my environment,
starpu_combined_worker_get_size() always returns 1
and only 1 thread runs in #pragma omp parallel for loop.
OTOH, vector_scal example run 2-4 threads (although I expect 6 workers since
the CPU is 6-core sandy bridge).

So, here are my questions:
(1) How does StarPU determine the number of combined workers ?
(in other words, why vector_scal runs 2-4 workers and my code runs only 1?
What causes the difference?)

(2) Is there any way to let (or even force) StarPU to use a certain
number of workers, i.e.
just as the same number as of physical cores.

I know that splitting the code into multiple tasks are preferable option,
but we have existing OpenMP code and we don't want to do that.

StarPU version : starpu-1.0 branch, rev. 5648
hwloc : available.

Regards,
Keisuke

--
------------------------------------------
FUKUDA, Keisuke<fukuda@matsulab.is.titech.ac.jp>
Dept. of Math. & Comp. Sciences
Satoshi Matsuoka Lab.,
Tokyo Institute of Technology





Archives gérées par MHonArc 2.6.19+.

Haut de le page