The super short answer is: 1.6.x is old and deprecated; can you upgrade to the 1.8.x series?
The short answer is "no" -- paffinity calls should never block, but it depends on how and what you're measuring.
The more detailed answer is: your trace below looks like it includes a call to MPI_Abort. Did your process hang during the abort, perchance, and (somehow) get stuck in a process affinity call?
Are you able to download and run the lstopo command from the hwloc suite? (http://www.open-mpi.org/software/hwloc/v1.9/)
On May 30, 2014, at 2:47 PM, "Lecrenski, Stephen K PW" <Stephen.Lecrenski_at_[hidden]> wrote:
> I am running some performance tests (Open SpeedShop) with a program which uses Open MPI and Infiniband.
> I see a line of code which appears to be taking a considerable amount of cpu time in relation to other pieces of the code.
> opal_paffinity_base_get_physical_socket_id (libmpi.so.1.0.8: paffinity_base_wrappers.c,118)
> Exclusive CPU time in seconds.
> % of CPU Time
> Statement Location (Line Number)
> Is this normal behavior?
> Stephen Lecrenski
> High Performance Technical Computing
> Pratt & Whitney
> 400 Main Street
> East Hartford,CT 06108
> Telephone: 860 - 557 - 2895
> Email: Stephen.Lecrenski_at_[hidden]
> P Please consider the environment before printing this e-mail
> CONFIDENTIALITY WARNING: This email may contain privileged or confidential information and is for the sole use of the intended recipients. Unauthorized disclosure or use of this communication is prohibited. If you believe that you have received this email in error, please notify the sender immediately and delete it from your system.
> devel mailing list
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: http://www.open-mpi.org/community/lists/devel/2014/05/14915.php
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/