Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-04-01 Thread Lenny Verkhovsky
Hi, is there any elegant way to register mpi parameter that will actually be pointer or alias to hidden opal parameter ? I still want to leave opal_paffinity_alone flag untouched but instead expose mpi_paffinity_alone for the user. thanks Lenny. On Mon, Mar 31, 2008 at 2:55 PM, Jeff Squyres wrot

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-04-01 Thread Jeff Squyres
Unfortunately, we have no way to "alias" an MCA param. :-\ This topic has come up a few times over the past few years, but no one's actually extended the MCA params infrastructure to support aliasing. I'm guessing that it wouldn't be too hard to do... On Apr 1, 2008, at 5:22 AM, Lenny Ve

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-31 Thread Lenny Verkhovsky
OK, I am putting it back. > -Original Message- > From: terry.don...@sun.com [mailto:terry.don...@sun.com] > Sent: Monday, March 31, 2008 2:59 PM > To: Open MPI Developers > Cc: Lenny Verkhovsky; Sharon Melamed > Subject: Re: [OMPI devel] RMAPS rank_file c

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-31 Thread Terry Dontje
Jeff Squyres wrote: On Mar 27, 2008, at 8:02 AM, Lenny Verkhovsky wrote: - I don't think we can delete the MCA param ompi_paffinity_alone; it exists in the v1.2 series and has historical precedent. It will not be deleted, It will just use the same infrastructure ( slot_list parameter

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-31 Thread Jeff Squyres
Sorry, I missed this mail. IIRC, the verbosity level for stream 0 is 0. It probably would not be good to increase it; many places in the code use output stream 0. Perhaps you could make a new stream with a different verbosity level to do what you want...? See the docs in opal/util/output.

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-31 Thread Jeff Squyres
On Mar 27, 2008, at 8:02 AM, Lenny Verkhovsky wrote: - I don't think we can delete the MCA param ompi_paffinity_alone; it exists in the v1.2 series and has historical precedent. It will not be deleted, It will just use the same infrastructure ( slot_list parameter and opal_base functions ). It

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-27 Thread Lenny Verkhovsky
NO, just tried to see some printouts during the run, I use in the code opal_output_verbose(0, 0,"LNY100 opal_paffinity_base_slot_list_set ver=%d ",0); opal_output_verbose(1, 0,"LNY101 opal_paffinity_base_slot_list_set ver=%d ",1); OPAL_OUTPUT_VERBOSE((1, 0,"VERBOSE LNY102 opal_paffinity_base_slot_

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-27 Thread Jeff Squyres
Are you using BTL_OUTPUT or something else from btl_base_error.h? On Mar 27, 2008, at 7:49 AM, Lenny Verkhovsky wrote: Hi, thanks for the comments. I will definetly implement all of them and commit the code as soon as I finished. Also I experience few problems with using opal_verbose_output

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-27 Thread Lenny Verkhovsky
> -Original Message- > From: Jeff Squyres [mailto:jsquy...@cisco.com] > Sent: Thursday, March 27, 2008 1:38 PM > To: Lenny Verkhovsky > Cc: Ralph H Castain; Sharon Melamed; Open MPI Developers > Subject: Re: RMAPS rank_file component patch and modifications for review > > A few more comm

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-27 Thread Lenny Verkhovsky
Hi, thanks for the comments. I will definetly implement all of them and commit the code as soon as I finished. Also I experience few problems with using opal_verbose_output, either there is a bugs or I am doing something wrong. /home/USERS/lenny/OMPI_ORTE_DEBUG/bin/mpirun -mca mca_verbose 0 -mca

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-27 Thread Jeff Squyres
A few more comments on top of what Tim / Ralph said: - opal_paffinity MCA params should be defined and registered in the opal paffinity base (in the base open function so that ompi_info can still see them), not opal/runtime/opal_params.c. - I don't have a problem with setting the paffinity

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-26 Thread Ralph H Castain
I would tend to echo Tim's suggestions. I note that you do lookup that opal mca param in orte as well. I know you sent me a note about that off-list - I apologize for not getting to it yet, but was swamped yesterday. I think the solution suggested in #1 below is the right approach. Looking up opal

Re: [OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-26 Thread Tim Prins
Hi Lenny, This looks good. But I have a couple of suggestions (which others may disagree with): 1. You register an opal mca parameter, but look it up in ompi, then call a opal function with the result. What if you had a function opal_paffinity_base_set_slots(long rank) (or some other name, I

[OMPI devel] RMAPS rank_file component patch and modifications for review

2008-03-26 Thread Lenny Verkhovsky
Hi, all Attached patch for modified Rank_File RMAPS component. 1.introduced new general purpose debug flags mpi_debug opal_debug 2.introduced new mca parameter opal_paffinity_slot_list 3.ompi_mpi_init cleaned from opal paffinity functions 4.opal paffinit