On Mon, Jul 23, 2012 at 10:33 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> So maybe that is the problem. PETSc is forcing affinity to a hardware > number core regardless of whether another PETSc program is running and has > also forced that same core? Yes. Now what's the right solution? Not set any affinity by default? Inherit the process affinity and subdivide it among threads? There is currently a somewhat crude mechanism in -threadcomm_affinities. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120723/3d7e57ba/attachment.html>
