Objet : Developers list for StarPU
Archives de la liste
- From: Mirko Myllykoski <mirkom@cs.umu.se>
- To: samuel.thibault@inria.fr
- Cc: Starpu Devel <starpu-devel@lists.gforge.inria.fr>
- Subject: Re: [Starpu-devel] CPU core binding mask and worker creation.
- Date: Wed, 24 Oct 2018 10:50:09 +0200
- Authentication-results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=mirkom@cs.umu.se; spf=Pass smtp.mailfrom=mirkom@cs.umu.se; spf=None smtp.helo=postmaster@mail.cs.umu.se
- Ironport-phdr: 9a23:sOT02BTUuW05eB5IRcmzxtov0dpsv+yvbD5Q0YIujvd0So/mwa69bBeN2/xhgRfzUJnB7Loc0qyK6/+mATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfbF/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4rx1QxH0ligIKz858HnWisNuiqJbvAmhrAF7z4LNfY2ZKOZycqbbcNgHR2ROQ9xRWjRODYygYIUBAeoPM/hFoYb/qVsArhS/Cge3CePzyDJIhGP60bEg3ug/FwzNwQwuH8gJsHTRtNj7M6YSUfq2zKnP0D7NaPNX2TP56InIcRAhpuqMXbFxccHMzkQvEgLFjk+TqYziOjOYzfgCs3OB4+p9UOKvlnQrqxpvrTW2wMonl4rHhpoNx1zZ+yh13Jw5KcO2RUN/e9KpH4dcuzuEO4Z2Ws8uXX1ktDonxrADuJO0ZzQGxZE5yBPaZPGLb4eF7g7mWeuUIDp1h3Roc6+liRmo60iv0Oj8W9G00FlUqipFlcHBtnUX2BzS7siLUOdy/ly71TaS0gDT9/tIIVsqmqbDKp4hxKA/loYLvEjeECL6hF/6gLGYe0gg4OSl5Pjrbq/4qpKcL4N0jxvxMqUqmsyxG+Q4NQ0OUnCe+eS9zr3j/kr5QLBRg/IqianVqo3aJcEGpqKjGA9azJ4v6wyjADe+zNQYgX4HIUpeeBKblYfpIUnOIO3hAfiinVusjilkx/TdM73lA5XNNWTDkKz7cbZy5U5czxAzzd9B6J5OC7EBJujzWk7ru9DCAB85KV/8/+GyE9x4y44aH36PA6WQLafOmV6O/OMmZeeWN6EPvzOoDvk/5PmmqG49nU4eerKq3NNDbXGiHfNjC06CJ2fpn5EaHDFZ7UIFUOX2hQjaAnZobHGoUvd5v2ljUdP0PcL4XomoxYe58mK+F5xSaHpBDwnVQ3zzMZiBRrEXZXDLe5Mzonk/TbGkDrQZ+1S2rgajkuhsNazJ/zBerp+xjIEotd2Wrgk78HlPN+rY02yJSDgqzGYBRjtw17s5vElgjEyOg/B1
- 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,
On 2018-10-24 10:21, Samuel Thibault wrote:
I'm wondering whether that should be set the default, or the current
behavior should be set the default (an environment variable would allow
to choose which behavior is wanted anyway). I'd tend to prefer migrating
to that new behavior.
The current approach can lead to odd behavior if the binding mask is set to something else that all available PUs. It seems that multiple workers end up running on a same PU and StarPU does not even warn about that. I think that the library should at least warn that this is happening.
My modifications do not handle the case where the binding mask is empty (hwloc-bind does not even allow that). However, I am not sure what happens if hwloc/kernel is somehow miss-configured/buggy. The library should probably report an error and abort.
In addition, if STARPU_NTHREADS_PER_CORE is set to a larger value than 1, then my modification will probably cause the code to hag if the cores do not contain enough "activated" PUs and/or the CPU does not support hyperthreading.
- Mirko
- [Starpu-devel] CPU core binding mask and worker creation., Mirko Myllykoski, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Samuel Thibault, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Mirko Myllykoski, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Samuel Thibault, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Mirko Myllykoski, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Samuel Thibault, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Mirko Myllykoski, 24/10/2018
- Re: [Starpu-devel] CPU core binding mask and worker creation., Samuel Thibault, 24/10/2018
Archives gérées par MHonArc 2.6.19+.