Something I should have mentioned. The paffinity_base_service.c file
is solely used by the rank_file syntax. It has nothing to do with
setting mpi_paffinity_alone and letting OMPI self-determine the
process-to-core binding.
You want to dig into the linux module code that calls down into the
plpa. The same mca param should give you messages from the module, and
-might- give you messages from inside plpa (not sure of the latter).
HTH
Ralph
On Jul 19, 2009, at 7:54 AM, Chris Samuel wrote:
>
> ----- "Chris Samuel" <csamuel_at_[hidden]> wrote:
>
>> I'll carry on digging.
>
> I've been trying to track back from the linux
> paffinity module to find some useful debugging
> info I can get my teeth into and I can see that
> the file:
>
> opal/mca/paffinity/base/paffinity_base_service.c
>
> seems to have lots of useful debugging message that
> should output what processes are getting bound where,
> but they are often conditional on the diag_requested
> variable. It seems that diag_requested is set based
> on this logic:
>
> if (4 < opal_output_get_verbosity(opal_paffinity_base_output)) {
> diag_requested = true;
> } else {
> diag_requested = false;
> }
>
> But I can't see what I have to set to make those messages
> appear! I've been through the output of ompi_info -a in case
> there was something listed there but nothing leapt out at me.
>
> Any clues please ?
>
> cheers,
> Chris
> --
> Christopher Samuel - (03) 9925 4751 - Systems Manager
> The Victorian Partnership for Advanced Computing
> P.O. Box 201, Carlton South, VIC 3053, Australia
> VPAC is a not-for-profit Registered Research Agency
> _______________________________________________
> devel mailing list
> devel_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
|
![[Flag]](../../../../../community/mirrors/flag-us.gif){kind=small}