Objet : Developers list for StarPU
Archives de la liste
- From: Olivier Aumage <olivier.aumage@inria.fr>
- To: Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>
- Cc: starpu-devel@lists.gforge.inria.fr
- Subject: Re: [Starpu-devel] Main thread not bound
- Date: Mon, 17 Feb 2020 16:27:50 +0100
- 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 Philippe,
The main thread belongs to the application code. Thus, StarPU refrains to
bind it and to modify it in any way unless explicitly requested.
--
Olivier Aumage
> Le 17 févr. 2020 à 16:19, Philippe SWARTVAGHER
> <philippe.swartvagher@inria.fr> a écrit :
>
> Hello,
>
> I discovered that the main thread of StarPU isn't by default bound to a
> dedicated CPU, unless I define STARPU_MAIN_THREAD_BIND. Why that is not the
> case ? Isn't it better for performances ?
>
> --
> Philippe SWARTVAGHER
>
> Doctorant
> Équipe TADaaM, Inria Bordeaux Sud-Ouest
>
> _______________________________________________
> Starpu-devel mailing list
> Starpu-devel@lists.gforge.inria.fr
> https://lists.gforge.inria.fr/mailman/listinfo/starpu-devel
- [Starpu-devel] Main thread not bound, Philippe SWARTVAGHER, 17/02/2020
- Re: [Starpu-devel] Main thread not bound, Olivier Aumage, 17/02/2020
Archives gérées par MHonArc 2.6.19+.