Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] StarPU 1.3 RC1 + peager problem

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] StarPU 1.3 RC1 + peager problem


Chronologique Discussions 
    < Chronologique >      < Discussions >
  • From: Samuel Thibault <samuel.thibault@inria.fr>
  • To: Mirko Myllykoski <mirkom@cs.umu.se>, Starpu Devel <starpu-devel@lists.gforge.inria.fr>
  • Subject: Re: [Starpu-devel] StarPU 1.3 RC1 + peager problem
  • Date: Sun, 24 Feb 2019 19:15:37 +0100
  • Authentication-results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=samuel.thibault@inria.fr; spf=Neutral smtp.mailfrom=samuel.thibault@ens-lyon.org; spf=Pass smtp.helo=postmaster@hera.aquilenet.fr
  • Ironport-phdr: 9a23:UoF/LRSS/EpkjCjL0jU14LBDh9psv+yvbD5Q0YIujvd0So/mwa6ybBKN2/xhgRfzUJnB7Loc0qyK6/CmATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfbB/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4rx1QxH0ligIKz858HnWisNuiqJbvAmhrAF7z4LNfY2ZKOZycqbbcNgHR2ROQ9xRWjRPDI28cYUBEukPPehXoIbhulQAohmxBQ6iC+701j9FhWX70bEm3+k7EwzL2hErEdIUsHTTqdX4LLocXvqwzKnV0zrDa+5d1yn96IjJaR8uu+yMXbZsccHMzkQvDBnKjlCNqYP7OzOZzPgNs2ia7+V7T+2vlmonqx1qrziuwMcskIjJiZgPxlDK7yV02YA4LsC7Rk5jedOoDZhduiGAO4doTM4vTXtktDsmxrEao5K3YTAGxIkjyhPccfCLboaF7x35WOuVIjp0nnJodK65ih2v60av0Pf8WdOx0FtSripKjN3MtncV2hzT9MeHUOFy8l271jaWygDT6+VELl4ylaXFN54t2LAwloALvUTCGC/5hln2gbeLekgn+uWk8frrb7voq5OGKoN4lh3yPr4zlsCnBOQ3KAkOX2yV+eSm073j+FX0QK5Qgf0zj6nWrpTaKd4Hpq65Ag9ayZws6wu7Dze6y9kXg38HLElcdBKDj4npPFfOLOr/DfeljFSgiC1ryOzePr39HpXNKWDOkKz9fbln8U5c0BczwclC6J1KFLEOPvbzV1T1tNzZFR85Lxe0z/zoCNVz0YMeQ22PDbGDPKPTt1+I/OMvLPOWaI8bojauY8Qistvvl3w+0XoMea243pwMa3HwSvFnOUaeZFLnmZEcFHpMpQdoCKTRlFSYSSMbS3usUqZ0sionAZi+EMLPS56ghJSF3TynBdtZaGdcBV3KEHHydozCVe1aOwyIJco0qTUBSLWlA7Mh1BunqQvmg+58J+/J9yleqZLi3tFo4/H7lBco9DUyAd7LgDLFdH19gm5dH2x+56t4u0Eojw7bifEp0cwdLsRa4rZyail/MJfdy+JgDNWrBlDMeMzMTEehRJOhGz5jFIttke9LWF50HpCZtj6GxzCjWudHlrqRBZVy/LiOhyGsdfY48G7P0ewat3djQsZLMjT31K5y7QGVDpfUkkGUkau2M6oGjnfA
  • 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>
  • Organization: I am not organized
Samuel Thibault, le dim. 24 févr. 2019 19:06:32 +0100, a ecrit:
> Mirko Myllykoski, le jeu. 07 févr. 2019 14:03:46 +0100, a ecrit:
> > I have been experiencing some problems with the new StarPU 1.3.0 release
> > candidate and the peager scheduler. I have reported similar/related
> > problems
> > earlier but I am quite sure that this problem did not exists with the
> > older
> > StarPU 1.3 nightly snapshots. StarPU 1.2.6 works just fine.
>
> Mmm, I'm wondering how previous versions could be working fine,
> actually. Perhaps just because the default scheduler back then was
> eager, you could try to set STARPU_SCHED=eager.
>
> I have dugged a bit, and what I found out is that basically scheduling
> contexts were never made to work with combined workers like peager/pheft
> uses, and a lot would need to be introduced and fixed to get this
> working.

Looking more into it, it looks like it was indeed only working by pure
luck: combined workers are added to the main scheduling context, and
peager happens to get them from there. But lws is not ready to see such
addition of supplemental workers, thus the crash.

Samuel


Archives gérées par MHonArc 2.6.19+.

Haut de le page