Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] hwloc CUDA plugin missing

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] hwloc CUDA plugin missing


Chronologique Discussions 
  • From: Alfredo Buttari <alfredo.buttari@enseeiht.fr>
  • To: Samuel Thibault <samuel.thibault@inria.fr>, Alfredo Buttari <alfredo.buttari@enseeiht.fr>, Brice Goglin <Brice.Goglin@inria.fr>, starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] hwloc CUDA plugin missing
  • Date: Mon, 11 Feb 2019 16:27:59 +0100
  • Authentication-results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=alfredo.buttari@enseeiht.fr; spf=Pass smtp.mailfrom=alfredo.buttari@gmail.com; spf=None smtp.helo=postmaster@mail-vs1-f68.google.com
  • Ironport-phdr: 9a23:L4oA/h8smZrCoP9uRHKM819IXTAuvvDOBiVQ1KB22+4cTK2v8tzYMVDF4r011RmVBdWds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2O2+557ebx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMNboRr4oRzut86ZrSAfpiCgZMT457HrXgdF0gK5CvR6tuwBzz4vSbYqINvRxY7ndcMsVSmpPXMlfVyJPDIChYYURE+UPMv1Vr5Xkp1YUsReyGRWgCeHpxzRVhnH2x6o60+E5HAza2AwgEcgOv2rJo9XyKawfTP21zLXUzTrZdfNW2Cr25Y/SfRAlr/GMR6x/ftfWyUU1DAzFk0mQqZD/MDOP1+QAqHaU7+x7Ve2xlWEnqgFxoiS1yscikInEn4QYwU3K+yV+xYY6P9y4SEhjbNG6FptQrD+VOJV3QsMiX2Fkoig6yqcAtJWmfyYK0IwqywDDZ/GDaYSF4RLuWPyPLTtlhn9pYrOyihW0/EO90OPzTNO030xPriddktnDqHQN1xvL58iCUPR9/0Oh1S+R1wDI9+1IOE40mKvYJpI7zb4wkZ0TsUvHHiDogkn5kKiWdkA89uip7eTofKnmq4eCO4NojgzyKKcjl8ylDegmLwQDXXKX9OW/2bH7+E32WrRKjvk4kqnDt5DaINwWqbS9Aw9byIYs9QuwDzC83NsDgHkHME5Fdwidj4joIFzOL/X4Au2+g1Soijtk2/fGPrj5DpXXMnfDiKvhfap660NE0woz0cpQ54hMCrEcOf78R1H+tMLGAR89KAG0x+fnCM5h1oMFQ26PDaGZMKTIsV+H+O0jOeiMZIkPuDb8Mfcp/fDujWVq0WMaKJKg2IYabDiEHvVsKlidfTK4md4EDGoO+BY+TebjlVmeeT9VfXe7GawmsHVzIYaoF4rPQciHnaCd1T26VslfYm5cB1yLV331a5mNQfYkZSSJL8JgkiBCW6L3D8cLzxCluUfVzLVjL+ycrgcCtJnukvdy6OnSkzkz8yZ1BoKTyTfJB3pol3kQWno60b5ypWR5y0yfyu53jftCGtEV5vVTUw58O4SP4fZ9DoXbXgzbc9uOAHy7XsmvGzB5Gts1zcUDb0E7Eci+khnZ3gKnBaQYmr2LGNo66PSPjDDKO89hxiOeh+EahF48T54KbDX+3/8tx03oH4fM1n6hueOvfKUY0jTK8T7an2WLtUBcFgV3VPecBCxNVg7ttd38o3j6Yfq2E71+aVlMz9WPJ6pKdpvnlwceHaqxCJHle2u03lyIK1OIy7eLNte4fmwc2GDDExFBnV5Du3mBMgc6C2GqpGeMVDE=
  • 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>

not sure I understand.

The documentation says:

"Note that the first workers correspond to the CUDA workers, then come
the OpenCL workers, and finally the
CPU workers. For example if we have STARPU_NCUDA=1 , STARPU_NOPENCL=1
, STARPU_NCPU=2
and STARPU_WORKERS_CPUID = "0 2 1 3" , the CUDA device will be
controlled by logical CPU #0,
the OpenCL device will be controlled by logical CPU #2, and the
logical CPUs #1 and #3 will be used by the
CPU workers."

so if I set

STARPU_NCUDA=4
STARPU_NCPU=20
STARPU_WORKERS_CPUID="0 1 12 13 2-11 14-23"

I would expect the four GPU workers to be bound to cpuids 0, 1, 12 and
13 and the CPU workers to be bound to cpuids 2-11,14-23. Instead here
is what the instructions in my previous email print

>>> 0 0 20
>>> 1 1 21
>>> 2 12 22
>>> 3 13 23
>>> 4 2 0
>>> 5 3 1
>>> 6 4 12
>>> 7 5 13
>>> 8 6 2
>>> 9 7 3
>>> 10 8 4
>>> 11 9 5
>>> 12 10 6
>>> 13 11 7
>>> 14 14 8
>>> 15 15 9
>>> 16 16 10
>>> 17 17 11
>>> 18 18 14
>>> 19 19 15
>>> 20 20 16
>>> 21 21 17
>>> 22 22 18
>>> 23 23 19

the second column, i.e., workers_bindid corresponds to what I set in
the STARPU_WORKERS_CPUID variable, the third, i.e., workers[i].bindid
does not and I don't understand what motivates the difference.

On Mon, Feb 11, 2019 at 3:59 PM Samuel Thibault
<samuel.thibault@inria.fr> wrote:
>
> Alfredo Buttari, le lun. 11 févr. 2019 14:59:52 +0100, a ecrit:
> > digging into starpu I found that starpu_config.topology.workers_bindid[i]
> > and
> > _starpu_config.workers[i].bindid are not consistent; is this normal?
>
> workers_bindid is either set explicitly in the conf passed to
> starpu_init(), or filled from the STARPU_WORKERS_CPUID environment
> variable, i.e. it is only what was requested, while workers[i].bindid
> is what is actually used during execution, which might differ if a GPU
> worker got bound to one of them for instance.
>
> Samuel



--
-----------------------------------------
Alfredo Buttari, PhD
CNRS-IRIT
2 rue Camichel, 31071 Toulouse, France
http://buttari.perso.enseeiht.fr




Archives gérées par MHonArc 2.6.19+.

Haut de le page