Thanks for the fix. https://gitlab.com/petsc/petsc/pipelines/96957999
> On Nov 14, 2019, at 2:04 PM, hg wrote:
>
> Hello
>
> It turns out that hwloc is not installed on the cluster system that I'm
> using. Without hwloc, pastix will run into the branch using sched_setaffinity
> and cause
Hi Barry
Maybe you're right, sched_setaffinity returns EINVAL in my case, Probably
the scheduler does not allow the process to bind to thread on its own.
Giang
On Wed, Nov 6, 2019 at 4:52 PM Smith, Barry F. wrote:
>
> You can also just look at configure.log where it will show the calling
>
You can also just look at configure.log where it will show the calling
sequence of how PETSc configured and built Pastix. The recipe is in
config/BuildSystem/config/packages/PaStiX.py we don't monkey with low level
things like the affinity of external packages. My guess is that your cluster
Google finds this
https://gforge.inria.fr/forum/forum.php?thread_id=32824&forum_id=599&group_id=186
> On Nov 5, 2019, at 7:01 PM, Matthew Knepley via petsc-users
> wrote:
>
> I have no idea. That is a good question for the PasTix list.
>
> Thanks,
>
> Matt
>
> On Tue, Nov 5, 201
I have no idea. That is a good question for the PasTix list.
Thanks,
Matt
On Tue, Nov 5, 2019 at 5:32 PM hg wrote:
> Should thread affinity be invoked? I set -mat_pastix_threadnbr 1 and also
> OMP_NUM_THREADS to 1
>
> Giang
>
>
> On Tue, Nov 5, 2019 at 10:50 PM Matthew Knepley wrote:
>
